> The store app doesn't add "App Paths" entries for "python.exe" and "python3.exe".

You're right, it's not following the aliases, but the actual executable. For 3.7, we had them as "python.exe", but from 3.8 they became "python3.8.exe" with a "python.exe" alias (python3.exe was always an alias). And since the App Path entries refer directly to the executable under "Program Files", you can (still!) only actually run them if you've also got the alias enabled.

You can test this by opening "Manage App Execution Aliases", disabling "python3.10.exe", and then pressing Win+R and launching "python3.10.exe". Re-enable the alias and it will run.

I believe it should follow aliases, since that's the only way the current logic works. I've already reported the bug that you can't launch without the global alias being enabled, and was told that it's "by design" and "better for users". But I'll see if I can find the owner of the feature and encourage them to fix it again.

> Python's installer puts the launcher in either the Windows directory or a directory that's in PATH, so there's really no need for an "App Paths" entry.

I believe there are some scenarios that search App Paths for "registered apps", but we already handle Open With just fine and I can't think what else matters, so you're probably right.