But the current Amtrak service is incredibly slow and inconvenient in both timing and destination. I just can't justify it, as much as I'd like to.
So I usually drive, occasionally fly. High speed rail (in 2099 or whenever they actually finish it) would be a nice choice. But if it's several times the cost of driving, not including the car I'd have to rent at the other end anyway, it will be a lot less appealing. The drive isn't that long, and even HSR won't be that much shorter.
I'd be a lot more likely to take HSR to Las Vegas, weirdly. There I don't need a car at the other end.
The Acela doesn't run in California and it doesn't run in Texas.
Trains in Eurpoe are going to 220mph.
http://www.bloomberg.com/video/take-a-look-at-europe-s-faste...
The average speed between NYC and Boston is something like 79mph. Saying you have a top speed 130mph, and doing it only for a small portion of the trip is quite misleading. At any rate, peak has little meaning. I've been on commuter trains that peaked at 90mph for 5 minutes.
I also don't understand your "peak versus average" speed thing. You're comparing apples-oranges, not me: I'm comparing peak-to-peak. Normal Amtrak trains also don't average 75MPH!
What these speed increases did was they made train travel roughly equal (well, probably within an hour or so) in time to plane for popular routes-BOS to NYP and NYP to points south. And given post-9/11 security, that made the train pretty attractive especially going downtown to downtown. I'd argue though that "faster" isn't an automatic win though. It has to be competitive with air.
The introduction of Acela also created a huge amount of publicity for taking the train rather than the plane
What higher speed rail could do in the Northeast is make the New England to the Pennsylvania/DC routes more attractive which don't really work for most cases today. But that's sort of a marginal and it doesn't address the more interesting cases where the economics and travel time math don't really work vs. air (e.g. NYC to Chicago).