If there is a turing complete VM inside the font renderer that makes perfect sense.
I'm not sure if it's the case but at one point on Windows, font rendering happened in the kernel.
Both Windows and Macintosh spent years trying to isolate type rendering from kernel operations specifically because of Adobe Type 1's legacy alone, including the fact that it was an ugly vendored 3rd party spaghetti. IIRC, both Apple and Microsoft ended up paying Adobe tons of money to rewrite their Type 1 Font Manager code from scratch rather than keep paying Adobe to write that code. (TTF and OpenType were also both somewhat direct responses to Type 1's legacy and mistakes.)
as an aside- I find the fact even microsoft's own modal dialogs don't all support DPI scaling- aka they are blurry.