Well, my machine is compliant, and I'm running Windows 11 successfully at the moment but I'm certainly not excusing Microsoft for this abrupt and surprising move that puts a lot of people out of the loop. Not to mention stressing the landfills with toxic waste and adding to some already inflated costs for new devices. It's a mess. MS may yet reverse some restrictions like cpu generation (to 7th) but something tells me it's gonna hold firm to just about every policy. Hope I'm wrong someday.
I think that increasing costs to the consumer just to be nasty and venal is not the plan. Microsoft is shifting a lot of responsibility security-wise to the end-user. Recall the Solarwinds attack becoming public knowledge earlier this year, when part of Microsoft's source code was stolen. Then, more recently, Microsoft signed off on a driver that turned out to be a rootkit (though intended for gamers in certain regions in China). Although that puts a ding in the Secure Boot idea, it's still moving along with the ever-increasing threat landscape. Just now, hundreds of corporations around the world were hit by ransomware at the same time, using a common network software. The group behind it is Russian based--some see it as an act of war already. That's how I perceive the rationale for making these hardware and UEFI-based security modules mandatory.
I believe Microsoft should have focussed on the Enterprise and networks running critical infrastructure first. This is affecting the private consumer division a little bit too much, imo. Who knows.