Increased granularity for MQ Event Message Delivery

I am looking for IBM to enhance the granularity of delivery options for MQ generated Event messages. While newer Event Message types such as Configuration Events get their own queue (SYSTEM.ADMIN.CONFIG.EVENT), legacy events share common queues. Authority, Inhibit and Start Stop Events all use the SYSTEM.ADMIN.QMGR.EVENT queue and there is no option to tune this. See the Use Case below on why one would want this capability.

One potential solution would be to create an Event queue for each Event type. To be backward compatible the new Event specifc queues for legacy Event types could be defined as Alias queues resolving to the classic local queues. Potentially new Alias Queue SYSTEM.ADMIN.AUTH.EVENT could resolve to local queue SYSTEM.ADMIN.QMGR.EVENT. The change would be transparent to existing users, but would give me the ability to change the Alias Queue SYSTEM.ADMIN.AUTH.EVENT however I see fit, to allow me to send Authority Events and only Authority Events where I want.

Another solution would be to convert Eventing in MQ to a pure Pub Sub implementation. With a strong topic tree structure covering all Event types a user could subscribe to very specific Event types or all Event types. And multiple users could have overlapping subscriptions, each one to the queue of their choice. Events lend themselves to a Pub Sub model where multiple users, a single user or no users might be interested in a particular event.