So now we can fairly say that, the server will know all addresses of an HD wallet will be know from the IP log or TOR circuit exit node information. No?
I'm not sure if I am correctly interpreting your question, but I think what you are saying is correct.
If your HD wallet software is connecting to a third party server in order to function (i.e. any wallet which is not running exclusively from your own node), then that software will query that third party server for the balance and transaction history of every address in your wallet. The third party server will then see a bunch of requests for different addresses all showing up at once from the same IP address, and can therefore be almost certain that all those addresses belong to the same wallet and are owned by the same person. If you are using Tor, the third party will see your Tor exit node's IP address; if you are not using Tor (or some other service such as a VPN) the third party will see your IP address.
If you then open a different wallet using the same software and query the same third party server, then that server will again see a bunch of requests for different address all showing up at once from the same IP address as before (whether that is a Tor IP address or your own IP address). It is possible then for the third party to link this second wallet to the first wallet by nature of the same IP address.
You can improve on this second problem somewhat by using a different Tor circuit and different third party server for each of your wallets. However, to completely mitigate both problems, then you must have your wallet software collect data exclusively from your own node.