LSF 10.1 fix 601504 the rate limiter

There is a request for the rate limiter(LSF_PROXYD_PORT).

All batch queries (bsub, bhosts, bjobs, bqueues, etc) connect lsfproxyd daemons to request token first. When they get token, mbatchd respond them and transmit data to these commands. 
These queries are from servers and client hosts. So DEV suggest opening lsfproxyd ports on all hosts, not only master.

I asked the support team about the port again and I received the message below again.
The ports configured by LSF_PROXYD_PORT is required to be opened for lsfproxyd to work normally. Specifically, the ports need to be opened for both incoming and outgoing directions for TCP.

What we want to ask is,

I would like to use the rate limiter for LSF_PROXYD_PORT through the existing LSF port instead of the new port.
For example, we hope to use one of the following ports as LSF_PROXYD_PORT.
LSF_LIM_PORT
LSF_RES_PORT
LSB_MBD_PORT
LSB_SBD_PORT
LSB_QUERY_PORT

Because, according to the customer, we can open a firewall port. But there is a problem.

Opening a firewall between LSF_PROXYD_PORT and LSF hosts is simple.
However, there is a wide variety of sections where firewalls should be opened. And the sections are very difficult to find.
For client hosts, for example, there is a wide variety of network area associated with these hosts.
In other words, it is difficult to find both the network/firewall between lsfproxy hosts and client hosts.

I know it's up to them to find the network section.
However, if the rate limiter service can be used as an existing port later, it will be a great help.