Minimizing the damage of the new update release cycle to modding

Recently I've heard that there will be a new release cycle that pushes out small updates sooner as versions like 1.19.3. This is great for the majority of vanilla players and probably for the dev team, but one group is being screwed over: modders. I know modders aren't technically playing how the game is intended, but mods will remain a big part of minecraft. I'm however worried that this new release cycle will force mod devs to stay on one version again and not update, like what happened with 1.12.2. And it's possible that people stuck on this new hypothetical 1.12.2 will despise new changes purely because they can't play with them. Another option for a mod dev is to keep working on the mod like it's fulltime job to keep it updated, which is simply not very sustainable. I'm sure I don't know everything, but from what I've heard, I can think of a way to minimize the damage. What I'd suggest is to make updates more 'compatible'. What I mean with this is that mods wouldn't have to update just to play on a new version that only adds, say, 3 new blocks. Mods are compatible with eachother. Mods are essentially content patches, and you can have multiple content patches at once. What I'm suggesting is to make smaller updates function more like content patches, so that modders wouldn't have to update as often. I get affecting modders was collateral damage for a more sustainable release cycle, but at least minimizing some of that damage couldn't hurt.