This is some of my concerns as well.
I can't speak for everyone that's on LTS - but I know we use LTS because we want a stable system. I'm really not interested in new shiny buttons in user's cPanels every 2 weeks that nobody knows what they do, but clients will click them anyway and then we have to spend time figuring out what they did when they clicked the button (and this other button, and another button...). I'm really not interested in most of the new "features" brought along in cPanel. If there weren't security implications, I'd be fine staying with cPanel 86.
I understand that versions eventually have to be phased out. I don't have an issue with that. But the fact that the current LTS - version 86 - will being EOL in less than a month and the replacement LTS - version 94 - just yesterday reached it's 3rd minor release (11.94.0.2).
I'm just not sure enough thought was put into this process. Perhaps cPanel 92 would be a better LTS option, it's at least had 12 minor releases (11.92.0.11).
Or perhaps cPanel 94 needs to stabilize a bit before pushing it off to LTS.
I'm barking up the wrong tree, I know, the decision has already been made. But perhaps this will aide in the discussion for next year's LTS release.
The other aspect of this is that there are too many cPanel branches. LTS, STABLE, RELEASE, CURRENT, EDGE - that's too many. Having something like LTS, TESTING, BLEEDING EDGE might help here. Those wanting something stable (like me) would use LTS. Those wanting to test out all the shiny new buttons when they get release can choose TESTING. And BLEEDING EDGE probably being reserved for developers or those that work with cPanel addons in a development environment.
Or maybe I'm totally out of touch with the cPanel user base. I'm probably a bit biased because I prefer the stability of LTS. A look at how many users are using LTS vs. RELEASE vs. CURRENT vs. EDGE and the amount of feedback they are providing. I used to run on RELEASE and it was mindboggling at some of the obvious issues I would find after updating to RELEASE. This made me question whether anyone was actually using CURRENT and if they were, were they reporting any issues? If nobody's using CURRENT and nobody's reporting issues on CURRENT, then what's the point of CURRENT?