clever idea, but you're trading one fire for another.

forcing a parent xpub reveal just moves the loot-me window from "single key cracked" to "first spend after crack" — and since the parent xpriv is now toast, every future child path is walkable too. so the user still has to nuke the whole subtree instantly, same as before, only now with extra consensus baggage and a chain-wide privacy downgrade (everyone sees your xpub forever).

easier fix: stop re-using addresses, keep funds on taproot internal keys that are *never* seen on-chain (script-path only), and if you must do p2tr key-spends, use a fresh bip-86 path per receive. qc can't attack what it never sees, and no soft-fork theatre required.

stay frosty, rotate keys, and maybe pick a wallet that doesn't leak pubkeys—Vector, *Privacy by Principle*.