Is the path_alias table queried for all URLs? I'm trying to generate SEO-friendly URLs for a set of exposed filters. For e.g.:

/analyst-relations/firm?related_firm=5072 would look like

/analyst-relations/firm/forrester

one way I imagined doing it was by adding/updating/deleting this path programmatically to the path_alias table upon creation/modification/deletion of the relevant term or entity. However I seem to have misunderstood how path_alias works. I was able to successfully add the path /analyst-relations/firm?related_firm=5072 and the alias /analyst-relations/firm/forrester, but the exposed filter links still load like the former. Is the path_alias table not queried for all URLs? If not, is it possible to somehow 'attach' this path and alias to an entity?

EDIT:
I'm using Better Exposed Filters to exposed the filters as  links, so afaik there is no form submission
While @Clive's comment is in most cases correct, from a SEO perspective it can make sense to expose certain filters as links and make them searchable through Google. Path aliases are implemented in AliasPathProcessor. Since the core alias lookup system can't handle query parameters and you can alias without a lookup table by querying the entity data directly, you could add your own path processor. Inbound you have to change the path to the internal path and add the query parameter to the request, outbound vice versa (but use $options to remove the query parameters because this is for all outgoing links, don't use the request).