I found this to be a real problem with using Arch in production. Updating is a bit of a catch-22: if you upgrade frequently, the workload of keeping up with the minutiae of not breaking your system is overwhelming. And the longer you leave it, the closer the chances of breakage when you do approach 100%. Result: you inevitably fall off the update treadmill at some point, usually during some sort of crunch time, and then never update again because who wants to tell their boss they spent a day debugging a self-inflicted problem? Safer to leave it alone and get on with your work.
This is why I switched back to Debian. Updating is stress-free and there's no downside to doing it as often as you like.
fwiw, I find the long term support pretty minimal. I'm only slightly more conservative in my use of`pacman -Syu` than I would be with `apt-get dist-upgrade`. If I notice a kernel or DE upgrade, I might hold off until the weekend on the off-chance that it needs a bit of extra maintenance. I appreciate handling these changes in smaller batches, as opposed to the 6-month system-wide major upgrade cadence. Of course, if I was just jumping between LTS releases, maybe only dealing with serious maintenance every other year would be an appealing trade-off.
(of course, I don't mean to undermine the argument for hesitating to jump to Arch on the grounds of maintenance. It certainly takes thinking about maintenance more often.)
This is why I switched back to Debian. Updating is stress-free and there's no downside to doing it as often as you like.