Steve, yes we used to make use in a similar way, in addition we said to run daytime patching if a PC had missed 2 patching sessions.
So in effect a loss in functionality with the new patch manager.
Something else to consider.
IF a machine does a day time patch, and the patch manager is not set to force the machine to reboot or nag the user; we don't nag as it annoyed users.
What happens is the next time the patch window comes around (typically 3 am), if the machine is in a pending reboot status (from the daytime patch) it won't reboot the machine in preparation. I'd have expected the patch manager to know it has a pending reboot and then do it, so it could then continue with more patches.
I found this out by speaking to Tech support.
We also have set the Windows 10 machines to not do "FastBoot", as when a user shuts down a PC, this was not completing the patch install. Only a reboot completed the patch - which users tend not to do.
We edit Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power\HiberbootEnabled to = 0
Do others have a similar issue / work around as we do?