Most of the implementation would likely need to be on the pacemaker end.
There is nothing like this currently, although these crm_mon options are somewhat related to ordering:
* --group-by-node shows the resources running on each node
* --brief summarizes resources by agent/node
If I understand the request correctly, a new "display-order" resource meta-data attribute would be a number, and crm_mon would show any resource(s) with display-order=1, followed by any resource(s) with display-order=2, etc.
Alternatively, maybe crm_mon could have an --order-by option with the possible values config (= default = current behavior), name, or agent.
I'm not sure at this point how intrusive or difficult either would be to implement. There might be a significant overhead from copying the resource list and sorting it.