Actually there is a bug in the GM.RUN_TIME PID (RUNTIME in BBL). It is incorrectly being multiplied by 160. It should display exactly the same value as SAE.RUNTM. I will fix it in the next update.
It is difficult to accurately link table B1832, since both those PIDs will reset to zero when the engine start cranking. The lookup used by the ECM for that table will most likely be a saved value of the previous engine runtime, not the current engine run time (as returned by those two PIDs). So realistically there should not be any link PID defined for the time axis on that table. (Unless there was a PID that simply defined the previous engine runtime).
Regards
Paul