I honestly see a problem with that limitations.
If message ordering is connected to Exclusive Queues then it means that you will have problems to scale ? Right ? That is exactly why kafka and some other order concepts (oracle web logic) base there ordering on groups or partitions (kafka).
Example:
Sales Order 1 - create
Sales Order 1 - update 1
Sales Order 1 - update 2
Sales Order 2 - create
Sales Order 2 - update 1
Sales Order 2 - update 2
Sales Order 2 - update 3
So you need all Sales Order 1 events in order and all Sales Order 2 events.
Like this you can scale to handle things in parallel per group/partition.
So my key question is how to handle in Solace ordering when i have to handle millions or messages per hour which require more then one consumer ?