Disclosure: I work for FusionAuth.
When we implemented passkeys a few years ago[0], we chose to implement them as a purely secondary authentication method. So you had to have an account, then you added a passkey.
So you have the normal account recovery process if you need it, while you get the advantage of passkeys for improved, faster regular login.
That's obviously a tradeoff.
I wrote up a bit about this issue[1] last year but I think there's been some progress on standardizing backups of software passkey private keys[2]. The idea of syncing around a private key, no matter how protected it is, still makes me a bit queasy (as it seems you are) but I understand the motivation.
0: https://fusionauth.io/docs/lifecycle/authenticate-users/pass...
1: https://ciamweekly.substack.com/p/on-webauthn-and-passkeys
2: https://www.w3.org/TR/webauthn-3/#sctn-credential-backup