I could be wrong here, but I believe it's quite possible to listen on multiple queues simultanously. You'd use the SelectConnection in pika (http://pika.readthedocs.org/en/latest/connecting.html#adapters-select-connection-selectconnection), fire up its IO loop as in http://pika.readthedocs.org/en/latest/connecting.html#io-and-event-looping, and it would select() (or what the OS favors) between multiple queues.

The advantages are…
1. We don't have to manually tie projects names to queues and reconfigure when projects move around—for example, when a project matures or scales up and moves off the generic cluster.
2. We don't have to write the UI or design the config files to support (1).

Seems like a clear win to me. You? We could still maintain project and queue names separately, for cosmetics, but I've probably leave that out of 1.0.