CfB can offer a minimum bound on bandwidth required for 1000 TPS (1 MBS) but can't say how many NXT service nodes that can handle the full blockchain are required.
I forgot about a very important detail. 1000 tps @ 1 Mbps assumes that we use
binary protocol. Now all data in protocol is encoded in
JSON, this adds 3x-5x overhead.
We have to migrate to binary protocol before switching TF on.
Have you considered well-tested compression tools?
I know it is tempting to define our own binary syntax but it's far more error-prone than using a matured solution. Another issue is giving up text-based syntax flexibility, expandability and fast and easy debugability. Just speaking from experience, my own and of others (some of which have failed because of that).
I don't know how experienced JL and you are when it comes to software engineering but I strongly advice you to consider different solutions.