If Google Maps is better at finding connections than Amtrak's own website is, then I think something is amiss that does not just concern foamers.
Google Maps generally is dependent on the GTFS feed from the carrier, in this case Amtrak, though it will mix and match with other carriers, like Greyhound. I just checked and the current issues with Builder/Lake Shore Limited connections show in Google Maps, they are just as messed up as they currently are on
Amtrak.com itself. Although Google Maps does show Greyhound connections from Albany that Amtrak itself would not.
Amtrak.com linking with Google Maps would just show the same connections as
Amtrak.com does itself already, it isn't "finding connections".
Google Maps isn't magic. It uses an API exposing Amtrak's own data, and is subject to the limitations of that data.
If this is true about Google Maps accuracy, then, maybe Amtrak should throw out whatever system they are using and incorporate Google Maps into their system. Lots of other folks do just that
The existing implementation of Google Maps is precisely the other way around, as explained above. Transit systems that use Google Maps for trip planning are still dependent of the transit systems' underlying systems and their data exposed through GTFS. They are just using Google Maps as their UI instead of developing their own. The data is from the carrier. Google Maps can be no more accurate than the data it consumes.
And, yes, before we get to it, I agree that Amtrak's website UI/UX design is very poor, the technical term, I think, is "sucks". But the data is the same.