The OP picture looks like bios display message , does not require any OS to do that. It's at the chip level reading the low level format of the drive.
Much like a built in message the bios would give you if there was no disk in the machine, except then the message is contained within the bios.
By wiped it simply means OS and user data are written over (often multiple times). It does not mean it is empty.
I understand what you are saying about the BIOS vs the OS and user data vs. the low level format of the drive.
My point is that a properly (<-IMHO) wiped drive, if you were able to just read the raw data, would literally be all addressable sectors completely filled with 256 or 512 bytes of zeros. (Little secret - the drives I worked on would keep track of which sectors were known empty, and if the host requested the data from those sectors, would give you a pre-filled buffer of zeros instead of reaching out to the media to "read" the zeros from the media. That way you get the correct answer but you get it faster.)
If a drive has anything but zeros, then it's not really wiped (again IMHO). Even a low level format that lays down a file system writes some data to sector 0 and I believe possibly some other sectors (2048, 4192, etc. maybe?). This is file-system dependent, but the data is non-zero.
Maybe they're just using a different meaning to "wiped" and my opinion is simply wrong/misinformed. Wouldn't be the first time.
And as a last point, you're correct in that the data is overwritten multiple times on traditional hard drives at least. There is a Department of Defense standard for the patterns to be overwritten and the number and sequence of those patterns. It has to do with the fact that traditional hard drives are read and written via magnetic fields, and if you overwrite just once or twice, there are advanced tools out there that can still "sniff" the remnants of the field and retrieve the data.
On the newer drives I worked on (SSDs), if they were encrypted drives, then it was faster and easier and just as secure to throw away the cryptographic keys - the data would still be there but it was complete gibberish. Of course you had to ensure that the keys were completely erased; I'm not sure how that worked exactly because the crypto stuff always seemed like waaay overkill (but the crypto guys were good at explaining how paranoid you have to think to cover all of your bases - we even had to worry about someone hijacking the SSD controller or the firmware, so the controllers had special encryption locations that needed to be carefully initialized for everything to work. Bottom line, don't forget your drive encrypt password or your data is gone forever and nobody can get it back, not even the SSD manufacturer.