For now my needs in that regard are covered by Backbone's router. It happily allows multiple instances of router (one for each context, was my thought) and bind all routes to Backbone.History.

My question was more with regards to what parts of handling routes would be good candidates for commands, etc. I'll write a (discussion) issue on it in a bit.