You didn't specified which "btc_address_dump" tool that you've used, was that from 10gic's GitHub repo?

Because you must have an incorrect derived address since that tool doesn't check for the mnemonic phrase's checksum and just assumes that it's valid.
Then, your 17-words backup phrase isn't a BIP39 seed phrase that can be used to derive your private keys and addresses.
That is for the recovery of your account credentials like what you did initially (when you got your password from it).
When you entered it to that tool, it forcefully used BIP39's algorithm to derive the displayed address, but that isn't what Blockchain(dot)com used to derive your keys.

If you used the new 12-words seed phrase in your security settings, that should be BIP39 standard.
However, the tool only derived one address while Blockchain uses more than just one.
And also, the one you're looking for could be from an address derived from the uncompressed public key pair of one of your prvKey.
And lastly and more importantly, the private keys from 2014 version of Blockchain's online wallet shouldn't belong to an HD seed since it's not yet implemented there yet at that time.

On the other hand, dumping the private keys from your wallet.aes.json file will ensure that every private keys in the dump file are the ones contained in your wallet.

You didn't specified which "btc_address_dump" tool that you've used, was that from 10gic's GitHub repo?

Because you must have an incorrect derived address since that tool doesn't check for the mnemonic phrase's checksum and just assumes that it's valid.
Then, your 17-words backup phrase isn't a BIP39 seed phrase that can be used to derive your private keys and addresses.
That is for the recovery of your account credentials like what you did initially (when you got your password from it).
When you entered it to that tool, it forcefully used BIP39's algorithm to derive the displayed address, but that isn't what Blockchain(dot)com used to derive your keys.

If you used the new 12-words seed phrase in your security settings, that should be BIP39 standard.
However, the tool only derived one address while Blockchain uses more than just one.
And also, the one you're looking for could be from an address derived from the uncompressed public key pair of one of your prvKey.
And lastly, the private keys from 2014 version of Blockchain's online wallet shouldn't belong to an HD seed since it's not yet implemented there yet at that time.

On the other hand, dumping the private keys from your wallet.aes.json file will ensure that every private keys in the dump file are the ones contained in your wallet.