I want to be woken up if something doesn't come back, not if it does or even if it has gone into limp mode.
Seriously you're looking at the wrong end of the problem.
But others are not like you. Systems are not always 100% foolproof, people don't have comprehensive DR plans.
Is it that hard for you to understand why someone may want to be up when there is a reboot? Like seriously?
Someone who thinks they can test all possible failure scenarios is severely lacking in imagination.
Sure there are more possibilities, but these should all be covered with a complete fallback DR strategy i.e. if not identifiable cause X, Y or Z then assume the worse, snapshot everything for debugging later and fallback to a complete restore from scratch.
The trick is to make X, Y and Z self-healing and part of your architecture provisioning.
I get the feeling most people here haven't dealt with large deployments and multiple site redundancy, five-nines reliability requirements and extensive DR planning, because the above is pretty obvious to those of us who have.
Even with our company which has in in-house ops team and our own colocated kit, we expect process failures and restarts and plan accordingly. No sleep is lost even when something explodes at 2AM (other than for the ops team, who in this case you contracted out).