Especially when much of what is "masked" couldn't be prevented by any program (short of complete aircraft inspection at every station with full spare parts invetory) at any cost with any MX system.

IMO this is 10% inquisitive in nature trying to get to the bottom of some key delay metrics and 90% about permanantly reducing block hours for the same amount of flights flown. I'm sure someone knows the number of pilot jobs we gain/lose for every minute per flight of more or less block hours. They mentioned an average 5 minute latency reduction target. How many pilot block hours does that equate to? How many pilot jobs does that equate to? That's what this is about. We will shrink as a result of this, probably by several hundred pilots when its all said and done, all things being equal.

Even if we never learn a thing about the operation doing this, the worst thing that will happen is D-0 takes a hit but A-14 (infinitely more important) remains about the same and at the end of the day we've eliminated probably at least a couple hundred pilot jobs. If we unearth a little nugget here or there (like jetway movement with 1 chock set instead of 3, etc) then great, but gate latency is merely the rebranding of the age old "wheel spin up" fantasy 'legislate by memo' for pilot pay and out times that pilot groups have been fighting off for many years all over the industry.