What would the value added be for never embedding fonts? I can see it simply providing one solution to letter dropouts issue in combined PDFs, but having searchable text is definately value added.
With our group, font embedment has always been an issue, as without all fonts on every page being embedded, you would have random letters drop out when you combine multiple pdf pages into a new pdf binder. The only solution was to guarantee that ALL fonts are embedded by ALL users,... and yes, it has always posed a "challenge" to assure complete department-wide compliance. Almost always the issue was with Arial, which was foolishly defaulted to be de-selected for embedment by Autodesk in versions prior to 2016. As i try to explain it to the novice users, not embedding your fonts prior to distribution is just like not binding or including your xrefs in an etransmit.
I quite like and am happy that Autodesk brought "Embed all fonts" out and made it FINALLY a defaulted value. It is EXTREMELY unfortunate however that they made all SHX fonts in PDF files readable via "Comments" rather than just using "Optical character recognition (OCR)" technology. This proves to be yet another insurmountable hurdle for corporate-wide adoption of the DWG to PDF driver.
Another "one-step-forward-and-one-step-back" by Autodesk. Frustrating is the first word that comes to mind when trying to describe this persistent tendancy of annoyances.
I too have toyed with the idea of converting SHX fonts to a TrueType format and completely getting rid of all SHX fonts in our templates. ...at this juncture, i sadly must conceed that it may be the best and only path forward with the DWG to PDF driver unless the next service pack eliminates the default appended PDF Comments for all SHX text.