Thanks for pointing me to the topic, tev
It is, indeed, possible to redefine the fonts
* if you want to permanently redefine the font, the most efficient way is to change section 2b of tiosmod+amspatch (which is, as the rest of that program, poorly documented), and as a bonus, benefit from the other improvements made by tiosmod+amspatch;
EDIT: more precisely, at the end of the 2b section, you'd write the binary data of your font through Seek(F_4x6_data), Seek(F_6x8_data) or Seek(F_8x10_data), then PutByte in a loop
* otherwise, you can use the attribute system to redefine them (attributes 0x300, 0x301 and 0x302), in either a TSR ASM program or a FlashApp.
TSR ASM programs are a pain, unless you depend on HW3Patch / tiosmod+amspatch; FlashApps also are a pain if you're running Windows Vista or newer: TI's severely outdated SDK doesn't run well on anything newer than Win XP, due to the dependency on Microsoft's non-standard JVM (which is very hard to find, at that).
Hardly anybody ever used the font redefinition support, because TI's font drawing routines are very slow: it's easy to make a custom DrawChar that is an order of magnitude faster than the DrawChar in AMS 2.xx and 3.xx... Therefore, basically everybody who needed custom fonts just embedded them into the program and used custom drawing routines.
Hope that this helps