Hello Manuel, hello Sujit,
About having 2 wdisp/system_0 parameters, the second one (in the order they appear at the profile) will overwrite the first one. So, only the second wdisp/system_0 parameter is taking effect.
About icm/server_port_1 to 3, you are almost correct, Manuel 
.
Notice that each of the parameters is binding the same port but under a specific, different IP address (this is because the HOST argument is being used). Since HOST is being used, this should not be causing any issues.
It seems that the parameter icm/HTTP/redirect_00 will never be used. But in case it matches a request, it seems it would cause an issue as it seems to be making the browser redirect directly to the Portal, bypassing the Web Dispatcher. But this would be something for a different thread, maybe .
About the "connection refused" error, ensure that your firewall (that is "natting" the public IP to the Web Dispather IP) is allowing connections to the TCP ports 8100 and 44300. Your firewall has to accept connections on these ports (at the public IP) and then "nat" them to the Web Dispatcher IP at the same port.
Then, test the connection to your public domain, specifying the port you want to use. For example:
http://www.your-domain.com:8100
or
https://www.your-domain.com:44300
Best regards,
Isaías