That depends on which distro and hardware you're using. I use laptops that are known to work well with Linux and Ubuntu LTS releases. This way, I spend perhaps 3-5h a year on admin tasks and it's mostly easy stuff.
It's actually amazing how GNU/Linux allowed me to gradually transition from configuring everything (when I was a student: XFree86, custom kernels, ...) to using GNU/Linux productively with almost zero housekeeping effort.
You can even try Silverblue. On the off chance something breaks, i do an rpm-ostree rollback, reboot and the system is on it's previous working state. I could troubleshoot stuff If I want to but I usually wait for an upstream fix before I update again.
I wanted to like silverbluez used it on the homelab as a host os for a while, went back to a normal server in the end, way less hassle.
Depending on what you want to do, you use the appropriate version.
Indeed if one is not willing/able to climb the learning curve of this paradigm shift, then they shouldn't use it.
I get why maintainers want to push flappypacks, I just don't care, it's a shit solution that leaks all over your users. Find a better way to fix your problems.
A hardware and software config + the goal (print)- and a dialog pops up, offering your solution as a line by line shell script.
All this stored in a trustworthy DB and even complex problems could be plug and play on windows. Add a "support" button to finance the whole thing.
Voila. Year of the linux desktop.
You might want to look into something less unstable.
I've had arch running unattended upgrades in a Cron for years.
Worst case I have to find my USB stick and do some debugging, not that an update has ever broken anything.
There is some minor maintenance I run maybe once every 6-12 months to clear caches or fix up any configs that need updating but I've never run into anything that prevents booting.