IDK. In the olden days, desktop printers sometimes had embedded font faces or PS1 fonts would be sent to the printer, but any vector file for large/high-res print quality had to be "ripped" or rasterized first, usually with a dedicated card. These cards definitely had signature looks and feels to them, but so did the fonts. There were differences between the way an Adobe Times New Roman would rip versus the one that came stock on your Apple IIsi.

Pinpointing a version of Windows, if it was printed from a stock OS font, could be as simple as comparing tiny differences in the vector files and knowing if one pixel would rasterize at 60% black versus 50%. To the extent that the rip goes through a graphics card, it would be knowing whether that card rendered the 60% as 58% or 62%.

I'm pretty sure if you scale it down, the printer driver will do an extra layer of downsampling and add its own anti-aliasing; but the printer hardware doesn't do that, it just sprays the dots it's told to spray, and in general the drivers replicate the pixels that are sent from Photoshop or in this case, MS Word, which uses something like QuickDraw used to be on a Mac, an embedded system process, to rasterize the fonts.