After experimenting with this, I think automatically issuing queries should be added at the same time/after the popups are removed. Adding this while still having popups makes the experience, in my opinion, an annoying interaction.

Does automatically issuing queries on move end (have to) imply showing popups for the query results? I think that can be a bit disorienting to screen reader users because they'll have (potentially a lot of) content announced for something they did not ask for and aren't necessarily interested in. Also, popups recieve focus when displayed, which is generally useful, but in this case it means a keyboard user can not continuously pan without having to close popups between each increment.

feature index

For the feature index use case, I think we'll want to populate that UI with identifiers of available queries, such that users can choose if/when to interact with them (issue queries). Is there such a thing as a query "name"?
Or do we need something like <link rel="query" title="(name to be displayed in the feature index)">? If that makes sense so that we can have query identifiers without issuing queries to retrieve such information (saves data, mitigates fingerprinting)?

I do realize that there's currently nothing indicating to users that queries are available, which this would solve in some sense, even if it may be annoying to some users. IMO we're probably better off focusing our efforts on the Feature Index in this matter.