Well based on your tracert , try to apply for that Gaming IP or static IP(if they provide at premium) on RailWire, see if it improves QoS:
Your routes just tell me one thing: Too many
routers in between which heavily loaded(more likely this is the case)
60 ms to
google DNS is
very bad
Here is your shortened tracert:
1 1 ms 1 ms 1 ms 192.168.0.1
......Routers playing PING PONG with your packet.......
8 17 ms 17 ms 16 ms 172.31.184.59 ---> Main REGIONAL router of RailWire
9 64 ms 23 ms 18 ms 125.18.192.93 ---> Here your packets are offloaded to Airtel
10 59 ms 59 ms 59 ms 182.79.198.2
11 52 ms 51 ms 55 ms 72.14.216.192 ---> You enter the Google's DC
12 63 ms 60 ms 61 ms 216.239.54.67
13 52 ms 55 ms 54 ms 142.250.228.221
14 60 ms 60 ms 60 ms dns.google [8.8.8.8] --> You get to the Google's Server in DC which handles DNS
Based on this , your pings to US EAST in best case scenario is 240 ms but more likely in 260-280 ms
This setup is not suitable for Work purpose.[if the pings are so bad for GDNS, VPNizing over GCloud won't help]
Try if there is any local ISP/ISP reseller who offers leased line, you might not get high bandwidth but if 10 Mbps leased connection works for your Amzn desktop then its great.
Ask your employer to compensate the bill.