Nat reflection is ALWAYS the worse option to choose.. I don't understand why anyone would ever want to nat reflect.. if host.domain.tld is on the same network next to you - then why would you not just resolve host.domain.tld to that IP.. Why would you ever want to go to the public IP to be reflected back in?? As to forwarding port X to port Y.. That is always a work around in itself to all to go to the same service with the limitation of napt and only 1 public IP, etc. If you want to go to host.domain.tld:port then go there where host.domain.tld resolves to the local IP and not the public ip..

Ok, final update. Eliminated everything that had to do with this VPN, interface, rules, etc. Started all over, following all the steps, and everything is working as it should, without the manual routes. By the way, if you run into the routing problem, you can change the "Gateway creation" to BOTH or to IPv4 ONLY and apply/save ont both server and client side(!) That creates the new route. Thanks all for your time and effort

@andyc Yeah, i want to have access to my ESXi management from work and at home. (only for a while, as I am preparing everything for my VM ect ..) i will make a IP restriction or something like that if it's possible, to allow only my home public IP and the work IP Or i can just do a VPN with my pfSense (i saw come options to do this), i don't know, i'll think about it