Not true for our ECUs. Not sure why you'd have any FF, duty cycle or pulse width displayed when none is happening. No injector frequency means zero fuel in reality. Reporting reality seems like a better idea...Well, yes and no.
It really depends on how software is written. Some simple examples are IAT (inlet air temperature), oil pressure, ECT (engine coolant temperature), MAP (manifold absolute pressure)... and so on. Once the ECU starts up, performs sanity checks, and fires up OS, these analog values will be read (via analog to digital converter), transfer functions performed, then appropriate values written to random access memory location specified. This happens regardless if engine is stopped (usually referred to as stalled), cranking, or running. I can't say this is universally true for all ECUs, but I can't think of anything I've worked with that doesn't act like this.
Now, MAP can be both time and crank angle dependent or synchronized (started time based then switches to crank angle burst mode).
As far as reading odd values with engine stopped. A good example is MAF (mass air flow) sensor, it is never truly "Zero" even when within specifications. Mess up transfer function (lookup table), or 2 point calibration with offset, and you can register sufficient mass flow with stopped engine to exceed normal idle state. How do I know, been there done that... Before anybody asks, no I didn't crank with such a large error.
So most OEM ECUs have sanity checks to identify such conditions and revert to a limp mode or simply don't start. But aftermarket ones are far more forgiving. Being forgiving they do need to display and log values, regardless of engine state, windowed (hole in case), stopped, cranking, running.
MAP isn't dependent on time or crank angle in our ECUs. Not sure why it would be. MAP is simply pressure in the manifold and you can read that even with the engine not running in our ECUs.
MAF is zero with engine not running in reality. Anything other than zero is false.
You can try to justify these errors if you want but in the end they are just plain wrong and the results of lazy programming. True data from logging makes it easy to understand what's going on. Erroneous data doesn't, as we see in this case.