I noticed this one line in your previous reply:

Because if it's just a simple list, you can already achieve that in BTCRecover by editing its "./btcrecover-master/derivationpath-lists/Electrum.txt" file.
But you should use a derivation path pointing to the target "chain_index" (receiving and change extended prv/pub key) and BTCRecover will search for the next level to match your given address.
The set defaults in the file only search the receiving addresses of legacy and SegWit script types from the actual master private (m) key to the "chain_index":

There, you can add an extensive list of derivation paths that you want to check,
And may be important; if you want to include change addresses, add lines with internal chain_index of each:
e.g.:
The gist is, add /0 and another one with /1 to your target account_index derivation path to specify the next level external (receiving) and internal (change) chain_index.

And lastly, the crucial part, for it to work just like how you ticked "BIP39 seed" option in Electrum while using an Electrum seed,
Edit the b"electrum" part in line #1736 in "./btcrecover-master/btcrecover/btcrseed.py" file into b"mnemonic".

Test output (electrum seed restored as BIP39 with Native SegWit BIP84 derivation path):

Note: if you don't know the address_index of your known address, specify a higher --addr-limit.
The token file; "sample_token-electrum.txt" contains the seed in specified order with achors so BTCRecover wont have to arrange it:

I tested this BTCRecover-1.12.0.

I noticed this one line in your previous reply:

Because if it's just a simple list, you can already achieve that in BTCRecover by editing its "./btcrecover-master/derivationpath-lists/Electrum.txt" file.
But you should use a derivation path pointing to the target "chain_index" (receiving and change extended prv/pub key) and BTCRecover will search for the next level to match your given address.
The set defaults in the file only search the receiving addresses of legacy and SegWit script types from the actual master private (m) key to the "chain_index":

There, you can add an extensive list of derivation paths that you want to check,
And may be important; if you want to include change addresses, add lines with internal chain_index of each:
e.g.:
The gist is, add /0 and another one with /1 to your target account_index derivation path to specify the next level external (receiving) and internal (change) chain_index.

And lastly, for it to work just like how you ticked "BIP39 seed" option in Electrum while using an Electrum seed,
Edit the b"electrum" part in line #1736 in "./btcrecover-master/btcrecover/btcrseed.py" file into b"mnemonic".

Test output (electrum seed restored as BIP39 with Native SegWit BIP84 derivation path):

Note: if you don't know the address_index of your known address, specify a higher --addr-limit.
The token file; "sample_token-electrum.txt" contains the seed in specified order with achors so BTCRecover wont have to arrange it:

I tested this BTCRecover-1.12.0.

I noticed this one line in your previous reply:

Because if it's just a simple list, you can already achieve that in BTCRecover by editing its "./btcrecover-master/derivationpath-lists/Electrum.txt" file.
But you should use a derivation path pointing to the target "chain_index" (receiving and change extended prv/pub key) and BTCRecover will search for the next level to match your given address.
The set defaults in the file only search the receiving addresses of legacy and SegWit script types from the actual master private (m) key to the "chain_index":

There, you can add an extensive list of derivation paths that you want to check,
And may be important; if you want to include change addresses, add lines with internal chain_index of each:
e.g.:
The gist is, add /0 and another one with /1 to your target account_index derivation path to specify the next level external (receiving) and internal (change) chain_index.

And lastly, for it to work just like how you ticked "BIP39 seed" option in Electrum while using an Electrum seed,
Edit the b"electrum" part in line #1736 in "./btcrecover-master/btcrecover/btcrseed.py" file into b"mnemonic".

Test output ():

The token file; "sample_token-electrum.txt" contains the seed in specified order with achors so BTCRecover wont have to arrange it:

I tested this BTCRecover-1.12.0.