Passkeys or WebAuthn are an open web standard, and the implementation is flexible. An authenticator can be implemented in software, with a hardware system integrated into the client device, or off-device.
Exportability/portability of the passkey is up to the authenticator. Bitwarden already exports them, and other authenticators likely do, too.
WebAuthn relying parties (ie, web applications) make trust decisions by specifying characteristics of eligible authenticators & authentication responses & by checking data reported in the responses. Those decisions are left to the relying party’s discretion. I could imagine locked-down workplace environments allowing only company-approved configurations connect to internal systems.
WebAuthn has no bearing on whether an app runs on a custom platform: that’s entirely on the developer & platform capabilities to reveal customization.
I question your reading comprehension. It’s much easier to claim something causes harm than to demonstrate it would.
History doesn’t support your assumptions: recalling the civil rights & free speech movements in the US, civil rights advanced despite similar free speech constraints I’ve advocated (eg, clear & present danger or imminent lawless action standard) and despite a harsher environment with Jim Crow laws and white supremacists speaking freely. Civil rights can advance with such narrow restrictions on free speech and have before when circumstances were worse.