https://storageswiss.com/2019/04/18/not-achieving-the-ssd-pe...
As for enterprise drives, there are dozens of tricks to ensure lower latency. Reading from other members in an erasure code, read prioritization over writes. It all depends upon how low of latency you’re trying to achieve, and with what level of consistency.
My point was that this drive may be using some innovative techniques to achieve consistently low read latencies in a “consumer” class drive. Possibly novel.
No it's not. This particular kind of incorrectly-designed application cannot be prevalent if the kind of hardware it requires to function at all is still new and rare.
But for normal use cases, you're either writing enough data that everything on the drive ends up refreshed at least once or twice per year, or you're writing so little data that your flash is basically not getting worn out at all and the retention times will be extremely long, so you're left worrying about read disturb errors which are pretty unlikely to grow into uncorrectable errors without a rowhammer-like workload.
I'm pretty sure most consumer SSDs are not doing full-drive scrubs after every power loss, both because I've never seen evidence of that while measuring SSD power consumption and because it would be insane to do given that it is common for the SSD to be completely powered off every time you close the lid of your laptop.
If you're worried about read latency on a scale that could affect an audio workload, the only change to the SSD that might be relevant would be disabling the low-power idle modes, which can take a while to wake up from. Enterprise SSDs have other measures to manage QoS targets that are tighter than what an audio use case requires, and those features are only necessary when dealing with a workload that includes a heavy volume of write operations—not relevant to audiophiles. And enterprise drives definitely don't need to duplicate all your data as a way of avoiding high read latency; it's possible to suspend write operations in order to service a read request that needs to access the same physical block.