Definitely a possibility -- LT is very flexible. Even if you choose to more or less ignore the plugin interface, you can interact directly with the DOM. I imagine the path of least resistance for a terminal plugin is just to open a new named tab via the API and then inject an existing HTML terminal emulator into it with access to the local machine.
I'm trying to picture this. So I have LT open, and then I interact with it via a 3rd party terminal application? Maybe the terminal app can "pull" output from LT (or LT "pushes" output to the terminal app?
You could certainly set up a bridge over sockets or ajax, but I think the true beauty of LT is that you can actually embed an extant web-based terminal directly into LT's dom and interact with its native events. LT runs in node-webkit, which is essentially chromium. The only barrier to entry I can think of is that it might be difficult to set up the terminal emulator to interact with the local FS, but its definitely a solvable problem. My current plugins both interact directly with the DOM and the local FS for various purposes using node and jQuery. The jQuery is honestly unnecessary thanks to only needing to support webkit, but it was a simple expedient and its luxurious not worrying about byte count since everything is running off the local machine.
