No the same port doesn't need to show on both local, and remote. It's a matter of finding the common port being used. Normally one of them will be using the same port, for multiple connections. Like for me on PS4 Call of Duty Modern Warfare, port 3074 is used on the local side to pass in game traffic, and I made a rule for that.
I will attach the two screenshots I grabbed after I stopped the connections from refreshing once I was in a game, not the game lobby, but in an actual match. As you will see port 3074 on the local is used, with the remote port side being a lot of different ports, trust me there's many of them, that image I only grabbed a few of the connections using 3074 on the local side. I didn't want to have a big screenshot, so I only included a smaller number of them. So when creating a rule, it's much easier to find the "one" main common port being used, and make a rule for that.
With that said, there was three connections using 3074 on the remote port side. Two using UDP, and one using TCP. I took the time to look up the IP's using remote port of 3074, as you will see by the start of the IP's, they're all the same. When I looked them up, all three came back to demonware. Which looking them up, COD, and a couple other games, use them for matchmaking/stats related data. Nothing I found suggest they're used to pass actual in game data. So I left these three connections under their default priority.
So I ended up making one rule, that was gaming related to COD. I selected UDP as the protocol, I entered 3074 as the local port, and finally, I selected in my case "Net Control Packets" as the priority to send it to. I found the two common ports that were used to pass traffic under "Net Control Packets" within my network, and rerouted that traffic to another priority. Anyways I hope all this isn't to confusing.
View attachment 20682
View attachment 20683