That's how they get you.
The shift off individual updates was for two reasons, neither of them to do with making your life easier. It was primarily to cut down on QC time at Microsoft's end, and they only had to test the roll-ups, not individual patches and their dependencies. Second is wallpapered over the crippling problems with the client side of windows update on 2016 and earlier releases. So many small patches would take longer to apply then the roll-ups.
This simple acted as an enabler for the worst habits of the update team. The stopped even pretending to do real QC after the roll-ups were introduced, and even with the rollups the 2016 and earlier update code was cripplingly slow. Instead of addressing this by backporting the update code to the earlier OS versions, they hoped we'd all just jump on the then brand spanking new 2019 server.
So we as admins/users collectively went from finicky individual updates that were slow, to monolithic updates that are also buggy and slow, but if one 4.5 rating CVE fix in the rolloup is bad, you have to uninstall the 9.8 rated RCE fix that's also in there. It's not faster, it's not more reliable, but when there is a problem the result is a long exploitation window with tons of visibility.
The better solution is to fix the updater and installers so fixes can be grouped and tested, but individually blocked or rolled back, and so a 25mb patch file doesn't take 45m and a reboot to install. Reboots should be for installing hardware.