Seriously, do you understand the word REMOTE?

From the man page:

> Journal events can be transferred to a different logging daemon in two different ways. With the first method, messages are immediately forwarded to a socket (/run/systemd/journal/syslog), where the traditional syslog daemon can read them. This method is controlled by the ForwardToSyslog= option. With a second method, a syslog daemon behaves like a normal journal client, and reads messages from the journal files, similarly to journalctl(1). With this, messages do not have to be read immediately, which allows a logging daemon which is only started late in boot to access all messages since the start of the system. In addition, full structured meta-data is available to it. This method of course is available only if the messages are stored in a journal file at all. So it will not work if Storage=none is set. It should be noted that usually the second method is used by syslog daemons, so the Storage= option, and not the ForwardToSyslog= option, is relevant for them.

That is all about local. Again: I end having to running a syslogd locally so that I can send stuff remtely using an industry standard protocol.

Your man page link confirms the capability is not there. It can forward to local syslog, which is still both useless (logging holes still exist) and needlessly redundant for this purpose.

You don't seem to have linked to any particular section of the man page. Linking the whole manual is not helpful.