Currently the intention is slightly shifted - to only "enforce" that shift to "the new content type" with a next dot-release (so not "v-next" but more likely the next half-yearly update ... and have that essentially be a pre-req for people to get the new content. That seems to walk a good balance and give people a good way of "controlling" that content upgrade step for themselves.
Keep an eye on the article, we'll likely update it as things develop -- this seems so far to be the best solution with folks being able to control everything for both sides.
For 2016, you should be fine for now, as it's an actively supported branch - so content for that will continue.
Does that help a bit?
If I understand correctly, the switch to Shavlik type patch engine would be in something like Landesk 2016.(x) and 2017.(x) and occur at least months from now. This would mean it a significant upgrade but IT depts can choose, it's not forced.
It seems to have been the best compromise that we could reach between the necessary & those who have difficulties uplifting their software stacks for whatever reason.