Regarding service-vs-client performance:
I took a quick look at the server side version and noted a few possible reasons for the lack of performance improvements.
In each of the inits you noted in your last post which I checked I found multiple calls to server side processes (for example the repetitive CreateHoursFromRange and CreateColumns services in FillTBODY), which would result in significant overhead.
Ideally you should refactor the init process so that there is a single server-side process (encompassing all the init processes together), which receives all relevant parameters from the client (if there are a lot of those build a parameter structure which will include all parameters and pass as a single parameter to the service). The service would output a complete tableContainer.
Regarding Convert Text to Number formatting performance, I could not confirm a performance problem running a simple standalone test on both client and server. Could you create a simple application demonstrating this?
Your idea regarding a style data structure, is an interesting one. Currently you might consider implementing a reusable model which receives such a structure and uses Set Style Attribute to set each of them separately (performance not withstanding).
For best results, use the Firefox browser..