Claude Desktop on Windows switched to being a WindowsApp which means that it's filesystem is now virtualized. A recent build has an escaped bug where it is trying to read the claude_desktop_config.json config file from the virtualized file system where it wouldn't be found effectively breaking access to MCP tools.
People keep reporting this issue against the Claude Code repo and they keep closing the bug because it technically is Claude Desktop, not Claude Code. There is no public place to submit this kind of issue.
That Snapdragon Kit you have was immediately recalled due to known issues. I read somewhere only a couple hundred ever shipped. I am one of the lucky ones to get one as well. If I were you I would get one of the Lenovo arm64 desktops and save what you have as a relic.
This time does feel different. The x64 emulation through Prism is a technological marvel and they just got AVX512 working which means that a lot more games will start to work. For companies that due pursue native ARM64 support, it's not all or nothing, there are ways to iteratively bring over pieces of that app. They also have this new App Assure program where they are working with both their customers as well as 3rd party app developers to get as much compatibility with existing apps as possible. Microsoft's previous attempts were silo'd platforms that weren't compatible at all with existing apps, so to me I see this eventually taking off like you say.
I don't think any games require AVX512 but the current x64 release emulator doesn't support AVX or AVX2 either which is needed by some games. The preview release of Windows for ARM does add support for AVX/AVX2.
People keep reporting this issue against the Claude Code repo and they keep closing the bug because it technically is Claude Desktop, not Claude Code. There is no public place to submit this kind of issue.