First of, welcome to the forum :wave: It is not often that we have somebody from Austria, and in fact I cannot recall a single (active) person in the Cento section.
Glad I could be of help. If you want to share your work with .xdf file feel free to do so. One thing I should note here is that there is an error in the checksum calculation that I provided. In short, it has to be done a bit differently and it cannot be done with the standard TunerPro checksum calculator, a separate plugin using TunerPro SDK has to be written (technically, the two bytes that follow the checksum location have to be an bit inverse of the checksum bytes). This has been recently pointed out to me (I actually knew it, but forgot that I did it wrong in this definition). Perhaps one day I can be inclined to do something about this.
Indeed there are several versions of the 16F program. This is due to the multiplicity of the cars and engines this ECU was used on, and also due to the multiplicity of software configurations (for example, supporting immo or not, having stepper autocalibration, having a slightly modified map design (again for example, WOT fuel map 3x16, instead of 1x16), etc, etc.). Minor things mostly, but it is enough to shift the data regions by a few bytes making one redo the definitions. It is somewhat better with the 8/18F(D) ECUs, still they also have at least 2-3 different program versions each with different map offsets.
In these IAWs there are two lambda switches, the one you talk about indeed kills the lambda correction altogether, the engine will never go into closed loop mode. The other switch "O2 sensor error" just disables logging oxygen sensor faults (if there are any this ends up in working in open loop again, but this is different).