Nah, there's a method to the madness on the bus in our operation. I've flown that flight number so I assume it's a bus in the scenario.
If you get a runway change, the other pilot announces that he's "heads down" and unable to help with the taxi. Change the runway, all performance data dumps, re-enter uplinked performance data, adjust and verify the runway/departure/first fix, then run the "boxed items" from the checklist.
That's IF you're a well-oiled machine. Runway changes, especially during my days in Flight Standards, is something simple, but can be the Achilles Heel of the flight deck, but we're trying to mitigate the threat/shock factor of the bus freaking out if the wrong performance data is in or missing (
USAirways Accident) or taking the incorrect lateral path off the runway and creating a loss of separation.
Now with the newest 321 NEO software, ehh, it's lunch time and I'm hungry. Maybe more later.
But if a pilot says it would be two minutes and it's not, have them clear the runway. It's as simple as that.
Line check? I'd certainly debrief the crew on "why did you take the runway with a plane on a ten mile final and an unresolved performance data issue? You underestimated the amount of time you would need, tower overestimated the amount of time they had, the aircraft is traveling at probably 3-ish miles a minute, 10 miles out? Your job is to make time, hold short run the procedure, run the checklist, circle back to your copilot and see where they are operationally and mentally for the takeoff".