You either have a long downtime or have a secondary ready to take over. I understand you're talking about avoiding to rely on a false sense of confidence; that's a good rule of thumb, but shouldn't get in the way of better solutions:
Test the secondary more often, and automate the recovery, and you'll cover more failure cases.
You don't have the resources for a secondary ? This means you're to small; neither this tool is for you; keep it simple, and just reboot.
Moreover, in some context is not desirable to perform a maintenance window until some designated moments like weekends. This means that you could leave your system vulnerable for up to a whole week.