It offers one advantage: You can run it in a GNU Screen session on a remote host.
(Unless it is somehow possible to run a graphical emacsclient over network)
Yes, you can use emacsclient over TCP. However for just editing files on a remote host there's no need to keep a persistent connection. Just use TRAMP, see section 18.14 Remote Files in the manual.
I know about TRAMP. But that's a different use case. In this case it's about keeping the Emacs session on a remote host.