All a traceroute tells you is where the packets are headed. The latency figures in them should only be used as a general guide. Most providers, Frontier included, have their network gear give a very low priority to ICMP (ping) packets directed at the gear itself so traceroutes can be skewed if there's a lot for the router to do, even if the link isn't saturated.
If the provider for your destination is willing, Frontier has partnered with at least one other large colo provider (SoftLayer) according to details in another thread here, so perhaps Frontier and the other provider can work something out for peering. You're right, however, that this isn't something a regular CSR or technician can solve. Perhaps there's something Ben J here can raise through Frontier but that may be beyond even his magical powers.