The first being that the code works fine, the deployment works fine, everything is working just fine. Do. Not. Touch. It.
These are some of the most financially important systems in America to date. It's not a question about if they have to work, it's a question about just how bad things would get if they didn't work for even a day.
The next problem that comes up is what happens when someone finds a bug 60, 40, or even 10 years in the future? What happens when some of this old hardware breaks and it becomes not only impossible to find replacement parts but also impossible to fabricate new ones in house.
Eventually, like all languages, Fortran will die out as time goes on. So few people know it now that it is inevitable.
Eventually something has to give and we can do two things until then.
1. Wait for time to pass and pretend nothing will ever happen to these machines.
2. Slowly start rewriting all of the stack, and transferring everything to more modern systems designed to be just as long term as their predecessors so that in the event of a replacement being needed it exists.
I don't know about anyone else, but I like to have backups/fallbacks when planning for the future.
I'm not saying that Ruby or any new language should be entrusted with this kind of responsibility. But there needs to be a decision and it needs to be made over the next couple of decades.