Suggestions are welcome, but they must be weighed against demand and development resources:
You chose a support topic with a question. Specifically you asked:
The answer was “no”, and multiple people gave suggestions for workarounds which you didn’t care for.
If you wish to open a feature request, please do so, however there are hugely more requests than can possibly be done. Also, developers sometimes work from GitHub issues because forum lacks tracking.
If you open a feature request in either place, please pick an appropriate title. Nobody will recognize the one used on this topic, otherwise I could simply change the category for you. Maybe you can post here:
which sounds like your request but only you know for sure. Your scheduling does puzzle me somewhat. Maybe you schedule for after you usually finish use, and if you stay later than that it will reboot on you?
shutdown (if that is what you use) does show a 30 second warning which you can make longer with /t.
If you’re willing to script, looking at time /t or %TIME% could be used to detect too-early-in-day backup. Example Scripts shows how you can stop a too-early-in-day run, making it wait for a scheduled late run.