I don't see the threat. How can anyone attack the Bitcoin network. Sure, some mining pools can be dd, but going solo mining or pool hopping will secure the integrity of the network.
There are a number of possible attacks (as I mentioned in my first sentence).
What if there is a bug in the client? What if somebody detects a flaw in the protocol? What if some cancerous nodes try to isolate a part of the network? What if somebody attempts a 51% attack (maybe after a DDoS on the pools)?
In each of these cases there are things that can be done to mitigate the damage, but the longer it takes to inform the right people, implement the necessary changes and roll them out, the more damage will be done to Bitcoin's reputation.
If there is a certain bug in the client, the devs might want to get the fix implemented at the pool servers as quickly as possible. Maybe merchants/exchanges would want to be informed that the Bitcoin network is currently in an unsafe condition and might want to temporarily stop processing Bitcoin transactions. If a hot-fix could result in a chain-split - who decides if this is the best/only way to fix the issue? What if some of the core devs are unavailable? A 51% attack could likely be prevented by activating stand-by hashing power but you'd quickly need a way to contact people willing to contribute their unused hashing power for this.
...
There simply are a lot of issues that could come up and might be dealt with sub-optimal when under time pressure.
Of course, a serious attack on Bitcoin may seem unlikely, but I think a kind of emergency protocol could really be useful in a crisis and certainly speed up the process of getting everything back on track.
