I'm reminded of the Xerox JBIG2 bug back in ~2013, where certain scan settings could silently replace numbers inside documents, and bad construction-plans were one of the cases that led to it being discovered. [0]
It wasn't overt OCR per se, end-user users weren't intending to convert pixels to characters or vice-versa.
I have to make a BOM and oh boy I hate my job
Love to give it to an arc client, not sure who the right person to implement this would be? Hmm…