pgquiles
Wt can be compiled to its own webserver (which you would use directy if on an embedded device oruse behind a reverse-proxy for other cases), or you can compile it to a FastCGI module you can run with Apache.
So:
1. It does scale and it's easy to scale. In fact, one of the use cases of Wt is massive applications (e. g. Facebook apps) 2. No, it does no interfere with client's ability to decide how they want to present the information. What Wt does is the same thing any other web toolkit is doing: gracefully degradation, fallback, etc depending on your browser, browser version, and whether you have JavaScript enabled or not 3. How is Wt's output not interlinked, clear-text, markup which the client renders?
It seems you only know Angular, React and other client-side toolkits. The server-side approach has been (an is still) working for decades, do not disregard it.
https://careers.mozilla.org/position/ohUW2fwT
IMHO Thunderbird should replace: - Gecko with Blink - XPCOM with normal plugins (I don't think anyone is making any real use of the unique features of XPCOM, e. g. the universal binary interface) - XUL with QML/WPF/alike.
Qt would provide a full-stack alternative: - Gecko -> QtWebEngine - XPCOM -> QPluginLoader - XUL -> QML
Maintainability and performance would increase exponentially.