Think about transceiver as "server" - this will help to understand. From TCI perspective, with regards it is Pro or DX - transceiver acts as TCI (websockets) server.
This server operates with to parameters - IP address (192.168.16.200 by default) and TCP port (ESDR2 default 40001, ESDR3 default 50001). It might be a bit confusing, because from above said it might appear that that IP "belongs" to transceiver and Port "belongs" to ESDR. However everything become clear if you think about "transceiver and ESDR" as the pair, which form single unique instance of ecosystem. (It also nee to be understood that when talking about ESDR3, we are talking NOT about launcher, but actual ESDR instance itself).
Hence, from above, what you need to do with IPs and Ports - is totally dependent on what topology you are going to run.
Couple examples for basic functionality.
Example 1. Only one transceiver is going to be active at the time within same LAN segment. Then - it is does not matter what IP and what Port are set. Both transceiver may have same IP/Port. All what need to be done is provide connectivity between transceiver and ESDR.
Example 2. Both transceivers are going to be active within same time / same LAN segment. Then - each transceiver has to have unique IP, but TCI ports can be the same.
When it does to SDC add-on, things may become a bit complicated, and this complication existence predominantly depends on how SDC is set up. SDC can be configured with profiles and profiles can be set with functions, which are differ for each - Pro and DX type. Hence, just need to watch it.