sit and wait. I guess it has to rewrite the whole table and its indexes. i.e. +190GB 
(I/O bound operation)
It all depends on the original datatype and length...

This will work when performing piecemeal restores (after primary FG has been restored):

Select ...
from sys.data_spaces DS
inner join sys.database_files F
   on F.data_space_id...

Already great work by Mark 🙂

I only came to this starting point:

Select  PlanXML.xmlnode.value('@FieldName', 'varchar(255)') AS FieldName
         , PlanXML.xmlnode.value('@FieldValue', 'varchar(255)') AS...

there seem to be a couple more parallel operations in the 58 plan vs the 3:45plan

Do you also monitor blocking operations in your system ?
Do these...

Best practices exist to be neglected.
Data consistency should not be dependant on the person doing the entry job.

replace " with no_wait" to "with rollback immediate" !

There can be dosens of reasons why a plan will get invalidated.
e.g. changes to indexes (rebuilds), create/drop index, statistics update, ...

Compare the old and the new plan...