EIP-155: How can we post signed Tx that do not have the EIP-155 chainID? In some recovery situations, this would be the only way to recover access.

I am working on a recovery case where a client has a very old Ledger device, and they lost they BIP39 seed mnemonic (but their ledger still have their seed and can sign Tx). The seed on their device controls very large funds in ETH and ERC20 tokens,

The firmware in the device cannot be updated, and it is only capable of signing pre-EIP-155 transactions, which do not include the chainID for replay protection. i.e. the "v" value in the signed Tx always 27 or 28.

See: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-155.md

Those signed Tx's are now rejected since the Berlin update, which enforces EIP-155, and we get:

Failed to broadcast the Tx: {'code': -32000, 'message': 'only replay-protected (EIP-155) transactions allowed over RPC'}

Is there a REST API (to submit ETH Tx's to the network) that has an option to ignore this check and still accept and process those old signed Tx's with no chainID?