A burst ban along with command synchronization is flawless, especially when 3 or more bots participate in it. I've seen this at Clan WaR@Northrend.
Hopefully, when I can get VectorBot to finally connect, I'll work on another project that I kind of started but halted (Synergy Co-Op). Either that, or I'll allow packet 0x13 on VectorNet to be a command receiver/synchronizing packet. It'll only work if you're connected with a certain product ID. (just called Bot Synchronizer). This idea may play out in time, and I see huge potential with this.
Your idea is ok, but it does lay open the possibility of flooding, whereas the burst ban froze the queue for 10 seconds or so before another burstban took place.