So I brought the produced clip to the timeline and cut out 4 seconds centered on the problem areas and placed them on the track below, then used SVRT. The SVRT track showed green everywhere except for the sections I wanted to repair, and it produced in a few minutes.
However, the SVRT produced clip was 5 minutes shorter than the source, and I found that PD had completely mangled a middle section of the clip.
When it reached the second image to be produced, instead of using the CPU and then resuming what should have been another 5 min section using SVRT, PD skipped right to the third image and then proceeded normally, completely missing the section in between the 2nd and 3rd repair clips. This is what shortened the clip duration.
Here is a content comparison just after the problem occured:

I have created a test project that uses an images as the new item in 6 places. The packed project, along with my SVRT-produced clip are available in this OneDrive folder. The total with the big clips is 16GB, but you could probably use any 48 minute (or longer) HD 60p clip already on your computer and simply replace my clip with it if you'd like to try this out.
I believe this is another facet of the SVRT "fix" that came out in 2314, which was due to the problems created in the earlier release, and so on. The core issue often doesn't ever get addressed, instead, bandaid patches get applied for specific situations which only increases the complexity of maintaining the code and significantly reduces its reliability

YouTube/optodata
DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors
Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°