You're missing the point this is DEFINITELY a workaround if you need to go through all that just to install a wonky security update that MS has released. We need to hold them accountable when they release these dodgy updates so they'll issue a proper fix and be incentivized to make sure future updates don't fail as well.
There are people who are not tech savvy enough to jump through a bunch of hoops to do the workaround just to install a simple update that should install automatically. I'm just not willing to put my main working studio system at risk by applying a workaround that shouldn't be needed. I have far too much valuable data on that system and many of the plugins and other software I own have not been tested for 21H2. I have had windows updates break copy protection for plugins before so it's never a good idea to update to a new version right away until developers have time to test.
If you wish not to hold MS accountable for their actions in order to force them to stop issuing buggy updates and put your system at risk that's on you.
But again I urge caution to anyone considering this workaround.
I will continue to pause updates until MS releases a proper fix as they did with the WasSMedic bug that we hounded them about for months.