It looks like your port that your torrent client uses is randomised. I think this is the biggest part of your problem. See, you need to have the port that your torrent client uses forwarded through from your router (often built into your modem) both in TCP and UDP in order to receive incoming connections. So… You need to pick ONE port and forward that port through to your computer. I'm not familiar with your particular IISP (provider - who I will not mention here for privacy reasons), or whether they offer connections on the DSL, cCable, or rCable platforms, (if I'm not mistaken, your area is under rCable territory), or even what hardware they provide you with your service, but if you PM me, I can work with you to get that port forwarding setup.
Also, just a heads up... If you're on the rCable platform, rather than bDSL, I would strongly recommend checking into your modem make/model to see if it is the Intel Puma 6 (or even Intel Puma 7) chipset, or if it is the Broadcom chipset. If you're on the cable platform and you're using a cable modem that uses the Intel Puma 6 or Intel Puma 7 chipset, I strongly recommend that for stability and optimal performance that you bridge the modem by turning off the "Residential Gateway" feature, then connect an external third-party wireless router to your modem to run your connection as these Intel chipsets are rather famous for their performance issues, and can even cause issues such as the one you are describing, dropped packets, random erratic latency spikes (even at non-peak hours), and in some cases, can even cause intermittent connectivity issues when the packet, usually when the packet is passing through the last-mile rCable platform to route into your IISP.... Just a heads up.
I know this all too well from personal experience with the equipment on the cable platforms in your area. Hopefully, you're either on the rCable platform with a Broadcom based modem, or even better for this purpose, would be piggybacking off the bDSL platfor to get a link into your IISP.