To directly answer your question, No. Ports listening or otherwise established on the loopback interface cannot be accessed from another system. This is by design, and were it to not be the case, the security vulnerability that would result would be catastrophic.
Localhost only ports are commonly used for Inter-Process Communication and services that should only be accessible locally.
In order to make your port accessible to the LAN, you must reconfigure the service to listen on an interface with a valid LAN IP or 0.0.0.0. The specific methods to do this vary by product, so you will have to consult the documentation for your product.
It is possible to write some kind of Application Layer Gateway that you could deploy on the host bound to a LAN interface, and proxy communications to a localhost port, but this will require a knowledge of network programming and the command syntax used by the application, which are not commonly available to system administrators.
--net=host
: doen't seem to open a port on either localhost or the LAN IP, and-p xxxx:xxxx
: which opens a port on localhost only.