"Home use" vs. "Enterprise/Data Storage" drive firmware with respect to data recovery?

[Quartz11]

So I was all ready to get an enterprise grade drive (Seagate Exos X10) when I saw this post:

 

https://community.wd.com/t/hard-decision-wd-gold-vs-wd-black/203332/19

 

"My understanding is the BIG difference between Gold and consumer (black and blue) is firmware. Gold is suppose to be used in a raid array. If memory serves the data center drives (gold and the Re series before) do not try and recover data blocks that go bad like consumer drives do. This causes data loss. Normally in a raid the raid controller will detect the bad blocks and fix the problem itself from parity data from other raid drives. If not fixed and it is a critical system file you can experience system instability or even worse total crash. Consumer drives a will try and fix this on there own but there can be pauses or delays when the computer asks for information and it is trying to fix it. In a raid array this pause would make the raid controller think the drive has critically failed and will drop it from the array to not risk corruption. "

 

(WD Gold is basically a rebadged HGST Ultrastar HC320--an enterprise drive.)

 

Is this true?  I do not intend to set up a RAID, only getting a single 8TB drive for a home desktop.  Is it detrimental to run a single enterprise HDD in a desktop system vs. something more home-use-oriented like WD Black?

 

P.S.:  

Here's an Intel document describing the differences between consumer hard drives and enterprise hard drives:

• https://www.intel.com/content/dam/support/us/en/documents/server-products/Enterprise_vs_Desktop_HDDs_2.0.pdf
• Section 3.2.1 "Bad Sector Recovery"
•       "Desktop drives perform heroic efforts to recover data in a bad sector.  ...  Typically desktop systems do not provide an online backup copy of the sector.  To recover data contained in a bad sector, desktop class drives are designed to attempt to re-read the sector many times before responding with an 'un-recoverable read error.'  During this recovery effort, the drive may become unresponsive and may ignore bus resets.  When the drive disappears from the bus for an extended period of time, the operating system, the application, and the user are required to wait for the system to respond.  A typical desktop drive command time out can take many minutes and no disk access is allowed while the system attempts to retry the command."     " Long drive recovery timeouts are unacceptable in an enterprise environment because multiple users can be affected...  A feature of enterprise-class hard drives is a time limited error recovery (TLER).  When a drive has a difficult time reading a sector and the short timeout is exceeded, the drive will respond by attempting to recover missing data from a sector checksum if available.  If that attempt fails, the drive will notify the controller and the controller will attempt to recover the sector from redundant data on adjacent disks and remap bad sectors related to the error.  ...  Typical timeout for an enterprise class drive is 7 to 15 seconds and retries are limited to a few attempts."

 

Hopefully it doesn't matter, as long as one keeps a close eye on S.M.A.R.T. data to look for presence of bad sectors, and replace the drive when those start appearing?