The problem is, those technically inclined members who could do it can already tell that it's not doable just from the OP_EQUALVERIFY error alone.

Basically, it's telling you that the public key in the scriptSig that your wallet has provided doesn't satisfy the condition of the locking script which is should be "equal" to its RIPEMD160[SHA256[(pubKey)] hash.

Since it's Electrum, inserting another extended public key onto an existing wallet is as easy as editing a text file. (unencrypt the wallet->swap the xpub->encrypt the wallet)
That will result with the high-value transactions associated with that xpub matched with the wallet's original xprv transaction(s) associated with that xpub matched with the wallet's original xprv (which obviously wont work during spend)

The problem is, those technically inclined members who could do it can already tell that it's not doable just from the OP_EQUALVERIFY error alone.

Basically, it's telling you that the public key in the scriptSig that your wallet has provided doesn't satisfy the condition of the locking script which is should be "equal" to its RIPEMD160[SHA256[(pubKey)] hash.

Since it's Electrum, inserting another extended public key on an existing wallet is as easy as editing a text file. (unencrypt the wallet->swap the xpub->encrypt the wallet)
That will result with the high-value transactions associated with that xpub matched with the wallet's original xprv (which obviously wont work during spend)