My apologies in advance, as this may upset some readers......
I would concur with what you said in this post.
The following is really get a bit off of this topic, but I think it applies to what @rpvw
has said. For the record, I haven't read through this entire thread, but I think I have the gist of what is going on. I have not yet upgraded to cPanel 68, for reasons I am about to explain.
I think ultimately what all of this boils down to is a complete misuse (or misunderstanding) of the various cPanel release tiers (STABLE, RELEASE, CURRENT, EDGE, BETA?). I'm assuming that this "feature" was included in v68 when it was at EDGE and CURRENT? But the issue did not really raise it's head until v68 reached RELEASE? Am I correct in this assumption? If so, this is telling me that there's not enough people using CURRENT or EDGE and finding these issues before the version moves on up the cycle. Either that or cPanel is pushing out versions too fast through the various tiers.
cPanel has attempted to remedy some of this with their new LTS schedule that went into affect this year. But it's still not a perfect system.
I'm not sure of what the exact solution is. But just because there's not an immediate solution, doesn't mean you can't identify it as a problem.
In my opinion, cPanel would be a bit better served if they simplified these release tiers.
Have an EDGE release that's mostly for developers - people that develop plugins and addon products for cPanel. Not really real-world ready
Have an LTS version - perhaps twice a year instead of the current once per year. Continue to support both versions (provide security updates) for 12 months. Another words release an LTS in January, release another LTS in June but continue to support the January release through December, and continue to support the June release through May.
Have something in between - call it RELEASE or CURRENT. This tier gets updated more often. Ideally you'd provide some type of incentive (lower price?) to use this tier, the idea being to get more people willing to use this tier and identify real-wolrd issues before it reaches LTS. This only works if you have a legitimate number of using using this tier and using it in real-word production environments, otherwise everyone is just going to be on LTS and only identify the issues when the release hits LTS.
This is one reason why I stay a bit behind the RELEASE tier (I suppose STABLE is more of where I'm at, but you can likely expect to find more issues with v68 when it reaches STABLE as even more users get the update). I stay tuned into these forums to see what "issues" might exist in various releases.
I know all of this is a bit off of the original topic here. But I just think this issue could have been avoided if it had been identified earlier in the release cycle.