@Blaze:
Unfortunately there are several places where your description is too unclear / ambiguous for me to be sure what you mean in those parts.

However some other parts of your description generally fit with the likely behaviour of Windows for (an unknown amount of) unreadable sectors on the original 3TB drive.
You need to decide whether you're going to try further DIY recovery, and take the risk that you might make the original drive unrecoverable (or at least much more expensive for a DR company), or pay for some professional help.
I'm not going to hand-hold you through the whole process, but if it was me attempting DIY without professional cloning equipment, I would be using appropriate Linux/Unix software (e.g. ddrescue) and direct SATA attachment, to try to clone the (encrypted) original disk, to the (also SATA-attached) replacement 3TB disk. Of course that's going to take a while, and due care needs to be taken of physical aspects like ESD etc. Obviously this means that you couldn't do the cloning using the laptops that you mentioned, as you would need at least 2 SATA ports and a bootable CD drive...
That cloning would do 2 things - it'll give a clue whether my guess about unreadable sectors is correct or not, and in many cases it'll be be able to read marginal sectors through using more retries than Windows does; and it'll produce a copy (not necessarily perfect, depending on the readability of the original) for any further experimentation which you choose to do, without further risk to your original disk. In fact depending on how it is used and the difficulty of reading any marginal sectors, ddrescue sometimes makes it look like all sectors on the source disk were readable (if you don't look for pauses during the cloning), when some were actually not readable by Windows, due to those limited Windows retries.
Other approaches to your problem are also possible - for example, it would be possible to scan the disk to check for unreadable sectors instead of cloning it, but cloning effectively does a scan anyway
and generates a copy for you, which is a "best practice" anyway. Some people may disagree with this approach...
Obviously the (still encrypted) clone target would then need to be attached via a working WD USB-SATA Initio board to do the decryption, before attempting to actually read / check the data using an OS.
There are risks with
doing cloning as part of DIY (the most obvious, but not the only, one being getting the direction of the clone source & target correct), and you may want to practice using other unimportant disks first. If you are unlucky, the source (original) disk might die during the cloning. There are also risks of
not doing cloning before DIY...
Also, ddrescue is not "one click" software, even if you are familiar with Linux/Unix, and while the typical default ddrescue commands are often partly successful, it can need interactive adjustments to the current command, for maximum success. Good DR companies have specialised cloning equipment, which is usually better than software-only cloning methods like ddrescue.
It's up to you how to proceed, based on the value of the data to you, and your confidence / skill / experience (which I don't know, and don't want to be responsible for). Your data, your choice
