The figures you're showing are pinging your own router, and look entirely consistent with a wifi connection. There's nothing VM or any other ISP can do to change the way wifi works, so what you've posted is going to continue unless you connect over ethernet. I'd also assert that a few local blips of an extra 10-40 ms won't be material within the inherent range of latencies on full round trip to a gaming server, and that itself will be as nothing compared to your 250ms+ reaction time.
That isn't to say that you don't have a latency problem, but it is to say that what you've posted doesn't show whether there is or not.
If you want to investigate a latency problem that is within VM's control, set up a Broadband Quality Monitor at Thinkbroadband.com, let it run for a few days, and post a complete 24 hour run here This is what a decent connection looks like - when gaming you'd be additionally overlaying the variability of wifi, but that won't show in your BQM.
As you can see, at peak times, peak latencies rise a bit, but nothing that's a real world problem for gaming. Bear in mind that if you're connecting to far distant, or over-subscribed gaming servers, then the latency will be materially worse than your BQM which shows the ping between Thinkbroadband's server and your hub, but what happens elsewhere on the internet is not VM's responsibility. Also, if you're running Twitch you deserve whatever you get do a check to see if stopping streaming has any impact - live streaming game video over a broadband and wifi connection is giving a much higher workload to equipment that's mostly cheap and cheerful, and may not play as nicely as you'd like.
What I found was that when it spiked when pinging my own router is when it would jump up in games, and lag out the discord audio slightly. Usually a 1-2 second delay. So the timings if those small blips match up with the latency spikes.
It's not only games, it's other applications too, but I'll run the checker and get back.
That isn't perfect, but equally we've all seen a lot, lot worse in this forum, and there's no reason why you shouldn't be able to game successfully on that connection. There's some peak loading in the morning (probably as people wake up and turn on every connected gadget they've got), and there's an unusual very early evening spike, but nothing major between 6pm and half ten.
There's no dropped packets, the average latency of your cable connection is within a range that looks to be 18-23ms, and most of the yellow fringing is inherent with the Hub 3 and DOCSIS technology. The peak time increase in latency is very modest, so I can't see VM wanting to investigate or spend money on this.
Unless there's other symptoms (slow speed via ethernet devices, or out of kilter SNR or power levels, or high error rates) then I think this will be regarded as an acceptable connection quality, and any spiking you're seeing in games is most likely either the upstream routing (mostly beyond VM's control) or down to the cable connection conspiring with the inherent faults of wifi (which is why ethernet is preferred for gaming).
Sorry if that's not the answer you want, but I can't see anything VM are likely to address based on the BQM, unless there's already a planned area upgrade that might fix the (implied) very modest congestion.
Well, before committing to leave, you might want to post your hub's Upstream, Downstream and Logs tabs here, so that people can have a look for anything that might be resolvable - costs nothing! Although VM won't care about gaming latency, they do want to keep the network within normal operating parameters, and it possible something's marginally adrift and worsens the peak time performance.
Also, log into the hub and see what the error performance is like. If there's more than a handful of post-RS errors then there's something wrong, or if there's many thousands of pre-RS errors.