Well, I don't notice any performance hit when increasing the text size in Works, and thereby using non-cached, anti-aliased fonts. The CPU-usage increases a bit when scrolling, but that's something I can live with.
Removing fntcache.dat would only lead to the file being recreated at the next bootup anyway...
The problem is that even though Win2k has an excellent anti-aliasing function, it caches some font sizes at startup. The cached font sizes won't be anti aliased, thus half the text on a page can be anti-aliased, whereas the other half isn't.
