The backhaul is a shared path
A satellite's backhaul carries traffic for clients behind that node. One 2.5GbE link can be plenty for ordinary internet use, but simultaneous local transfers and multiple wired clients can make the shared path the bottleneck.
2.5GbE is usually the practical middle ground
Choose 2.5GbE when the WAN, switch, NAS, and desktop are in the same general speed tier, the cable path is already in place, and no single local workload needs more. It is easier to deploy and often leaves more usable ports.
10GbE needs an endpoint on both sides
A 10GbE mesh port is useful only when the modem or ONT, switch, NAS, workstation, cable, and negotiated link can use it. A 10GbE port connected to a gigabit switch is still a gigabit path.
Wireless backhaul needs a different test
A faster Ethernet port cannot repair a wireless satellite placed behind too many walls. Compare wired and wireless backhaul separately, and keep nodes close enough for a strong relay before adding more hardware.
Check the port job before checkout
Mark which port serves WAN, wired backhaul, switch, NAS, and local clients. Mixed 10GbE, 2.5GbE, and 1GbE layouts can be faster on paper but less convenient than several equal 2.5GbE ports.