I looked at the match patterns again and a compromise solution might be to match something like https://*/search?* and https://*/search?*. This would match any URL with a path ending in search (and optional a query string.
Examples: https://mysite.com/searchhttps://mysite.com/search?s=mysearchterm
TODO: implement support for SearX/SearXNG