Wait... try enabling the MAF SES stuff and setting it to MIL on first error.
Also, for shits and gigs, I pulled my fuel pump fuse and cranked my truck to see how it acted. My injectors sort of hang out too, instead of dropping all the way off like I assumed they would.
On my tune, I leave the first few cells of the maf alone all the way up to idle because if you look back in my post history I was having trouble getting my truck to start, and it was because of the weird MAF code nonsense.
Apparently some years you can just uncheck the SES box. Some other years you have to leave it checked but set it to "Don't report." Some other years you have to leave it checked and set it to "No MIL error."
Basically the computer is failing the MAF, but not using the speed density table either, because you're telling it that it's ok to have a bad maf, and not to do anything about it. If you tell it that failing the maf is a bad thing, then it'll use the VE table. The only exception I know of is some oddball OSs that apparently don't care about the the maf failing and will just do its own thing regardless of what you say lol.
after idle adjustments slight stumble but ok.hpt- flex log
tahoe flex run to radleys shop.hpl- flex tune, look at MAF errors
after trans adjustments.hpl- gas log
park to drive enrichment, zeroed maf, stall saver, fans turned vats off.hpt- gas tune, look at MAF errors
Like I said, apparently different years have different requirements for the MAF errors. Idk why, as I said earlier, I'm pretty new to all this. I just recently found out about the MAF code stuff. Mine DEFINITELY had trouble starting until I got the MAF stuff worked out. I'd say re-enable the MAF codes and leave them like stock, SES checked, MIL on FIRST error will help it fail faster and start easier. MIL on second error was stock. Either way will work, just make sure that it either fails, and you go into SD, or enable them so the computer can use the readings.