Mystery partially solved. After picking the brains of a couple of technicians and a few people who deal with automotive computers, we figured out the cause of the P0442 code was due to the method that is used to detect small leaks and it's almost ridiculous how the error is triggered when there is no leak, and how to prevent it from happening.
In simplified terms, after the EVAP drive cycle is completed by either all the preconditions being met or by doing a service bay reset, this is what happens:
When you turn the ignition switch to the run position, the evap I/M test begins about five to ten seconds later. The vacuum to run the test is indeed supplied by the line to the intake manifold through the purge valve solenoid. *IF* the EVAP I/M drive cycle is completed and ready for the ECM to run the test, which, of course, it will at that point, and *IF* you leave the key in the run position for more than about 10 seconds without starting the engine, it will throw a "provisional error code" that will not trip the CEL until or unless it occurs during the next start up consecutive.
Thereafter, if you by chance don't start your engine almost immediately after putting the ignition switch in the run position (within five or ten seconds), there will be no vacuum at all on the EVAP system and when the test runs, it shows a P0442 code if a provisional code has already set. The next time you start after leaving the key in the run position for about 5 seconds or more before starting the car, the error code sets but will not trigger the CEL light until you start the car again (the third time). This is proved out by looking at the freeze frame data which show you all the normal readings for an engine that isn't running ( 0 RPM, etc.). I can reproduce the code by simply leaving the key in the run position for 5 or 10 seconds before starting the car, shut the engine down, do that again, shut the down again, and the third time you start the car, the CEL comes on and shows a PO442 on the scanner.
So, the easy solution is to immediately start the engine in one fell swoop when you put the key in the ignition within a second of moving to the run position. If you let it hang in the run position without starting, and EVAP I/M drive cycle is ready, you will inadvertently cause a bogus PO442.
It does have to do with the ECM programming, per se, but because the method used to run the test is itself defective in terms of way the program works. Reflashing the ECM (which I can do without a dealer) won't do anything unless the ECM firmware is corrupted in that particular routine, unless you alter the code in the firmware to run the EVAP I/M test only after the motor is running.