You need to transfer the entire ROM or its contents from patient to donor. That's because each ROM has unique "adaptive" data.
Microjogs are not a SMART parameter, so smartctl will tell you nothing. Each head has a read element and a write element. The spacing between these elements varies from head to head due to manufacturing tolerances. That's what microjogs are.
See …
HDD from inside: Tracks and Zones:
https://hddscan.com/doc/HDD_Tracks_and_Zones.htmlAs for the firmware and "adaptives" …
The hard drive -- a computer-within-a-computer:
http://www.hddoracle.com/viewtopic.php?f=56&t=2600&p=20704#p19087"Adaptives" -- why a straight PCB swap doesn't work in modern hard drives:
http://www.hddoracle.com/viewtopic.php?f=56&t=2600&p=20704#p19090As for imaging a failing HDD, professional data recovery companies have "hardware imagers" (eg DeepSpar) which interact with the drive at the firmware level. In this way they can stabilize the drive by disabling features such as read retries, spare reallocation, SMART, etc. These imagers can also disable selected heads, thereby enabling the good heads to be imaged.
Ddrescue and HDDSuperClone don't have control at the firmware level, so they limit their retries in software, and they skip over bad patches in the media during the initial pass. On subsequent passes they try to read the more difficult sectors. HDDSuperClone can execute at least one firmware trick which stabilizes some WD drives, and it has a better understanding of "zones" than tools such as ddrescue. Both tools maintain a log, so they can be resumed after an interruption.