Hey Ian258,
Thanks for reaching out!
After reviewing the screenshots included with your post it looks like you are referring to the packet loss/nonresponding hops in the middle of the route.
When you see all that packet loss show up in a trace, it's natural to think something is wrong. However, as long as this packet loss doesn't carry through to the destination, it's not something to worry about!
This sort of packet loss indicates that (hop #10,13,14,etc) is "de-prioritizing" or dropping ICMP Time Exceeded responses. This behavior affects only the returning information and does not affect forwarded packets.
If you're interested, here are a couple of articles that can explain this concept a bit more:
One Poorly Responding Router Interpreting Latency and Packet Loss Moving forward, I suggest running PingPlotter traces directly to your game server (which appears to be 52.203.3.55) while playing games to try and correlate in-game behavior with PingPlotter results. Along with that targets such as the Google DNS server (8.8.8.8) or the Cloudflare DNS (1.1.1.1) are both good targets to get a baseline for your network conditions.
Along with that, considering you have tried troubleshooting a large majority of your local/home network it is definitely possible for your network issues to be originating outside of your home network (hop 2 and on) however, I suggest collecting more PingPlotter data to help confirm/deny this.
Hopefully this helps, let me know if this leaves you with any additional questions!
Best of luck,
-TJ