What do you mean by "supported". I have configured TCC to be OpenSSH's default shell. It works but I have to be very careful. If TCC does anything GUI, the session will hang. TCC is capable of a lot of GUI stuff. Removing it all might be quite a chore.
Actually, correction: "Take Command Console". As for operations which bring up GUI/windowed elements--those would need to be trapped and set to fail/return an error code. [IF the session == SSH vs. Console, NO-OP+Error-Code any operation which would generate a GDI Dialog/Window/etc.]
ATERNATIVE(not too serious--this would be serious work): Re-implement GUI dialogs using NCURSES & TWIN(Textmode WINdow), Manager or similar "text-mode GUI" frameworks. [Over the years there have been at least half a dozen such platforms. Handy on low-bandwidth connections! For PC-centric users, have a look at the old DOS "DESQview" product by Quarterdeck.]
I noticed that if you SETDOS /i-help, HELP DIR gives the quick help in the console.
Is there a way to disable the likes of these (possibly with an alternate INI file)?
Beside what's affected by ConsolePopupWindows=Yes, can you give a list of those commands and variable functions which can create GUI interfaces (keystrokes too, like F1 and Ctrl-F1, if it's possible to disable them)?