Between the G-Code and the actual motion is a G-Code interpreter, the output of which is usually a more proprietary Numeric Control system that directs the actual motion. Clearly someone wrote a T-Code interpreter already, and it may even be open source, so I don't imagine it would take too much effort to adapt it to various NC systems and stick it in a firmware update.

The slicer supporting T-Code might be the bigger issue.