Right, so that trace is showing a normal trace for the Verizon network. Since the traffic is via HTTPS, unless the traffic is somehow being proxied through another host without interference, a MITM redirect or hijack would instalty raise red flags for the application being used, causing the connection to halt or terminate.
There's some data you can check within the Wireshark dump if you saved it to see if there's a transparent proxy being used. One key bit to check for is for the IP address of the source and/or destination. Source should be either your computer's IP if you're sending out, or the remote server's IP if receiving. Vice versa for the other direction. If something's different, you're getting pointed to what could be a proxy. What you're also looking for is the difference or delta between the time it takes for a SYN to be sent and a resulting ACK to be received. The latency betweeen the two should be within the range of the latency you get to the server on the other end. If you get 70ms of latency in a trace/ping and a normal initial connection setup takes something like 8ms to set up, there's a red flag right there. If it's taking same or even slightly more time than the latency to the server to set up, you likely do not have a proxy in the mix.
I would run the Netalyzer tool on your computer to see if it detects any sort of proxy. It won't display the technical details, but it does have a few proxy detection mechanisms in it, one of which is a Transparent proxy detection. It's not 100% reliable since ISPs can manipulate results, but I've never seen Verizon do such a thing.
At this point though, I would consider talking to Vudu a bit more, or trying the same type of Wireshark capture against your neighbor's Comcast connection. I suspect the problem is with Vudu terminating the connection due to their "proxy/VPN" detection system, unless they've checked and have claimed otherwise.
http://netalyzr.icsi.berkeley.edu/ is the link to Netalyzr