that's just not a thing. nintendo doesnt do anything to block atmosphere from working in new firmware versions. it's atmosphere intentionally preventing itself from running when it detects a potentially unsupported firmware version just in case the atmosphere patches happen to be incompatible
0.0.X firmware version updates are allowed because those are never breaking changes, anything 0.X.0 or X.0.0 atmosphere will halt if the firmware version isn't explicitly supported. 20.2.0 and 20.3.0 only needed to be marked as supported by atmosphere to work, the code for atmosphere 1.9.1 works perfectly fine on 20.2.0 and 20.3.0 otherwise
in every other case there are changes to the os that are incompatible and the cfw needs to be updated to fix it, this is exactly why cfw checks the os version and halts when it detects an unsupported version. if cfw just blindly applied patches then you break the os at best or the console ends up generating bad console logs that get you banned at worst
mad that people take nintendo updating and improving their os as "cat and mouse situation to try to block cfw" though. obviously if it weren't for cfw we would still be on firmware and sdk 4.0.0, the only reason why nintendo ever makes any changes to their code is to break cfw patches. disregard that people just don't update until cfw updates its patches, nintendo aren't stupid dude. nobody is trying or even expecting to break cfw on purpose with os updates. they are well aware of what it is and how it works. they know it's not possible to just "disable it" for those who are currently using it. they arent putting in all the time and money to work on their os just for the sake of making cfw not be able to run on a newer version for a week and it's kinda wild that people think this is the only reason nintendo ever updates the os