I'd like to point out some secondary context: Virginia is getting an additional train sometime in the next year or so, going into Norfolk. While I highly doubt that this would affect the NB Meteor, SB there's room for this to be the result of a cascade effect. Please do not forget that the SB Star is also "stacked" on top of a Regional (95/195) in one of the strangest scheduling decisions in that part of the world (seeing as the two trains are in the middle of a five-hour schedule "hole", and only avoid being stacked with 125 as well by dint of 125 getting parked at WAS for 50 minutes...otherwise you'd have three trains hitting RVR within an hour in the middle of a seven-hour "hole" from 1100 to 1800. By the same token, 97 chases 85 down the line (to the point that if 85 gets held up, it can foul 97).
Bear in mind that as of right now, the last train out of NYP that can make it into Virginia is 97, and 97 leaves at 1515. Pulling that backwards, it means I can't get to within a reasonable distance of home from Boston without leaving mid-morning. Likewise, there's NB connectivity to the LSL but no SB connectivity, leaving the only option there to be to use 67 (with no sleeper). Bluntly, this sucks.
A departure from NYP at 1900 would correspond to PHL about 2040 and BAL at 2200. Neither of these are awful times. WAS is getting on the late side...but to be blunt, with how badly Amtrak screwed the pooch, in all cases this allows getting a passable dinner prior to departure.
On the southern end, I would suggest that opening up more space between the Star and Meteor in SC, GA, and FL would probably help ridership as well...especially since it would do a better job of syncing daytime service at various stations: Right now, the NB train has its "daytime" cutoff at about Florence, SC (2300-ish) but the SB train has its cutoff at either Savannah or Jesup (0630-ish and 0730-ish, respectively). Likewise, the SB train provides decent times in VA (as I long experienced), but the NB train's times sort-of suck (0430, anyone?). The situation in SC and GA is the more important of the two since folks in VA heading north have other options. Folks on the A-line heading south of Savannah don't.
Anyhow...I think the culprit here is VA shaking up its schedules with the additional Norfolk train. My guess is that there are a few interests lining up for this: VA has a reason to want 91 to go "somewhere else" and probably wouldn't mind 97 doing so as well so as to cover other timing markets. Local traffic will divert to the Regionals (little or no net loss) while other riders can be scooped up in passing.
The only problem with some of the timing is access into NYP (and into the Hudson tunnels) around rush hour. Were I to redo the trains, I would probably try to get the Meteor in as close to the end of the rush hour slug as possible (1830 would probably be the ideal here, but 1900 may be the best that can be done for one reason or another). I'd probably edge the Star later (I don't know how late they can hit Raleigh without losing ridership, but if we go by the ballpark of 2300 that would give about two hours...and get 91 into the middle of a prime-hour "hole" on the Richmond line with a departure around 1700 from WAS since that slot's Regional goes to Roanoke), and it would also line it up quite nicely with 78 (as opposed to 76) and allow better times for Savannah and Jacksonville, while there's no connection to be lost to Charlotte in any event. I might also consider moving 91 earlier, but that risks cannibalizing 79's ridership if they get too close (while a later departure increases the differentiation).
For the record, I have no idea when the extra Regional VA is arranging is going to run...but I strongly suspect that it will result in a lot of trains moving around by varying degrees.