So you’re not remapping the source ports to be unique? There’s no mechanism to avoid collisions when multiple clients use the same source port? Full Cone NAT implies that you have to remember the mapping (potentially indefinitely—if you ever reassign a given external IP:port combination to a different internal IP or port after it’s been used you’re not implementing Full Cone NAT), but not that the internal and external ports need to be identical. It would generally only be used when you have a large enough pool of external IP addresses available to assign a unique external IP:port for every internal IP:port. Which usually implies a unique external IP for each internal IP, as you can’t restrict the number of unique ports used by each client. This is why most routers only implement Symmetric NAT.
(If you do have sufficient external IPs the Linux kernel can do Full Cone NAT by translating only the IP addresses and not the ports, via SNAT/DNAT prefix mapping. The part it lacks, for very practical reasons, is support for attempting to create permanent unique mappings from a larger number of unconstrained internal IP:port combinations to a smaller number of external ones.)
When it comes to their trademarks Valve can’t take a fully hands-off approach without negative consequences. Either they explicitly endorse the use of the Portal name and other branding, in which case they’re encouraging and aiding the project and could potentially be caught up in any lawsuit from Nintendo, or they say nothing and allow the trademark to lapse from non-enforcement, or they prohibit the project from using the Portal branding and enforce that prohibition with a lawsuit if needed. Unfortunately for the project, only one of these options retains their trademark and doesn’t set them up for a fight with Nintendo.