On the other hand I doubt that's intentional. Even as an avid Apple critic I want to mention that people I trust and are more involved with Asahi, always pointed out that Asahi received the occasional little help from Apple devs where possible (surely, not with official documentation, or confidential infos).
So, I would wait until things had time to calm down and not get too invested with Apple bashing.
A consumer shouldn't be restricted from installing their own OS on a device that they bought, be it a smartphone, tablet, laptop, desktop, or server.
A company the size of Apple should also be required to release proper documentation that enables the porting of operating systems to these kinds of devices.
The reverse engineering work that the Asahi team did is remarkable but so much of it is ultimately busy work that didn't need to be done if we regulated the consumer electronics market appropriately.
When folks say Intel and AMD are done, and we should all be on ARM, or RISC-V, beware of what to wish for.
Yes there are device trees now, however someone has to keep them up to date, and that is only part of what makes a motherboard.
Macs have always allowed you to run another OS.
iDevices have always had a locked bootloader.
People shouldn't confuse the two.
The actual problem was that Apple has an undocumented APFS key for if a volume is bootable, which Asahi wasn't setting and Apple wasn't checking, but now they do, so they do.
For every niche thing you wish that Apple or other third parties do only for your own enjoyment, there are hundreds of millions of other people who want different niche things. Buy the products that suit your needs and wants, and companies have incentive to make them. And if no company wants to provide a feature or function that you know a huge portion of people will want, then you have a golden opportunity to start a business providing this.
They’re 100% commodity hardware and fully locked down from any user freedom. Weirdly everyone focuses on Apple with all their might instead of gaming consoles.
In any case, though, Apple agrees with you, and they explicitly built support for non-macOS OSes into the bootloader. This is a bug in the first developer beta of a new release.
"A foreign power could potentially deny access to the OS" sounds like a compelling argument.

Asahi Linux is warning its users from trying out the new macOS 27 "Golden Gate" beta released this week by Apple. With macOS 27 beta, the Asahi Linux partition is no longer visible and thus unable to boot to your Apple Silicon Linux installation.
Whether it's an accidental bug by Apple or an intended change, Apple changed the boot picker and Startup Disk handling with macOS 27. Any Asahi Linux partition is still present and without data loss but is no longer visible and thus unable to boot for at least the time being.
Those that do try out macOS 27 beta, hopefully you have a secondary installation of macOS 26 or older to allow for booting your Asahi Linux partition in the interim.
Asahi Linux filed a bug report with Apple over this behavior change in macOS Golden Gate while they wait to hear more from the company. In the meantime they are warning users to avoid macOS 27.
In other Apple Silicon Linux news this week, Linux 7.2 is set to enable boot support for the Apple M3 devices albeit not yet usable for end-users and, well, if you haven't upgraded to macOS 27 Golden Gate.