The exchange you are using will obviously know all the addresses that you withdraw coins to. You won't have any immediate privacy against them, whether or not you reuse addresses.
However, if you reuse the same address, then in the future when you want to spend those coins, whoever you send them to will be able to see all of your past transactions to that ...
Will EVERY address I'll generate AFTER the passphrase will NOT be accessible to the old copy (Before the passphrase)
Correct. When encrypting a wallet, every key/address used from that point on will be new and encrypted. The wallet will not delete the old keys of course, otherwise it would lose all the funds before encryption. But from that point on, it ...
Here is a snippet code that demonstrate how one can create a Bitcoin address from scriptPubKey:
script_pub_key_hex = "410400d0ade32217e076945e0946ef7bed72d9aea035aa8891e4bf0749ae6e24f8a7d3ea56efafe472ac3943dbed3af7c093729720ac9ab04e8eba09286e3a00fe41ac"
# generate public key hash from scriptPubKey hex
P2PK scripts have the form PUSH <KEY> OP_CHECKSIG.
Means push 0x41 (65) bytes. This is followed by the public key (starting with 04 incidicating it is an uncompressed public key). Finally, 0xac is ...
I am afraid the sent coins are irrevocably burned.
The reason is that P2TR addresses encode a (tweaked) public key, while P2WSH addresses encode a script hash. If someone would take a P2TR address so that it is interpreted as a P2WSH address with the same payload, you'd need find a script that hashes to the public key in the P2TR address. This is completely ...