I should be able to adjust rank within Jira Agile, even if my query first orders by priority, then by rank

We have been using Jira Agile/Kanban for many years now. We recently decided that the Agile board should really be ordered first by priority, then rank within the priority. We also use swimlanes based on Epics, to organize our current features at the top.

This means that stakeholders priority tickets are pushed to the top of our Kanban board view, which helps us plan out the most important work.
In other words, the agile board shows tickets in the same order as stakeholder priority, and works well:
project in (MyPrac, PWS) ORDER BY priority DESC, Rank ASC

Currently Jira does not allow "Move to Top" or drag and drop tickets vertically in the Agile view, even though it does allow "Rank to Top" on individual tickets. (When viewing the as in:
https://issues.practichem.com/browse/MyPrac-1234)
Steps to reproduce:

1. Set up a Kanban board with a filter containing: ORDER BY priority DESC, Rank ASC
2. In the view, attempt to drag and drop the ticket vertically to adjust rank.
3. Or, Click on the ticket, observe that the side panel shows more ticket information on the right, then click on ... for additional actions, and then click "Move to Top"
4. Observe that Jira does not adjust the rank, and that it displays an error:
5. Ranking is disabled, as the Filter Query for this board is not ordered by ascending Rank. Please check your filter configuration.
6. Expect that Jira moves the ticket to the top of the rank within the given priority. I'd be fine with a warning, if you want.

There isn't any real reason to block the re-rank completely, since this is a scenario where we are using "atypical" queries. When people do use these ordering schemes, Jira should still allow the adjustment, as much as possible.

Since Rank is still relevant, and still part of the query (Rank ASC), I should be able to change the rank within a priority. (Rank to Top vs Move to Top).
Of course, I don't expect that drag and drop or "Move to Top" should affect priority. Without this, organizing rank of tickets becomes quite tedious.