Issues with ROM on SSD

SSD read disturb errors are a potential concern
The firmware would presumably prevent these by rewriting or relocating the block after "too many" reads have been made
Theoretically, these rewrites could in turn wear the SSD out
A back of the envelope calculation suggests that theoretically it'd take on the order of a million years until this problem would occur, assuming smart firmware
If the firmware maintains per-block read counts and they're retrieved by an intruder, this may potentially allow for early-reject of some candidate passwords (block never accessed? this password must be wrong!)
Mitigation: start using the ROM SSD half way through computation of a hash