Yes pretty much, It can be also applied even more loosely than the above (by only with "new" updates NOT hotfixes). Say for example You are currently on 2.1.0.123, and an update for 2.1.1.123 comes out without notice, then preceeding "hotfixes" come out for 2.1.1.125, 2.1.1.127, etc.
If I wait staying on 2.1.0.123 until all the "hotfixes" have been resolved, things have been settled down enough that you feel comfortable actually updating to by then 2.1.1.135, Currently there is no notice given that 2.1."2."123 is coming (as they are on average about 2 weeks apart) and when its released you MUST choose 2.1.2.123 "IF you want to update", without any option or warning that it's coming for you to get 2.1.1.135 before the process starts over.
So you must at some point (with the current policy) (IF you do choose to upgrade AT ALL) become an involuntary beta tester, and "IF" you have issues, then use the "platform roll back" feature. Requiring more work for every user for a simple update process, that preventive measures could prevent.
Yes this has stranded off to even more confusing subjects, like if something that is "rarely" used/needed takes up half of the page of the UI screen, and the "common use" for when issues arrive for users to use is in one line of small text with a "click here" link?
This POST is NOT in ANYWAY a criticism of HE, it is merely FEEDBACK for what would help us users, and I would assume help HE support by reducing support tickets.
