So I know already that I got the ignition fade out/in calls right, so that was piece of cake, thanks again! However, bypassing the fuel cut was so far very unsuccessful, my first attempt (by temporarily bypassing a small branch where B_bevab is set to true along with a couple of other things) resulted not only in the fuel still being cut, but also never coming back, or maybe not even that, perhaps the monitoring system did not like the configuration of the variables and shut down the engine, fuel cut or not. So 50% solution so far (with one pending test that can potentially solve the issue, but my guts tell me it won't).

EDIT: Looking at the actual code for DMDZAG tells me with very little doubt that the ignition cut and injection cut are requested separately, so I am not sure that the statement that ignition fade-out pulls in fuel cut automatically is actually true. I am not at the car during the tests to check this either, so I am still a bit lost.

EDIT 2: And the same conclusion looking at the immobilizer related cuts...

EDIT 3: the ignition / fuel not coming back in one of the attempts was a stupid coding mistake on my side. It all slowly clarifies now.

Since just now I came to this, if somebody else would need this in the future, this is how I explained it to myself:

This is the array of zwcalcar.
If zwcalcar_0=0xD00024C0, then zwcalcar_1=0xD00024C1, zwcalcar_2=0xD00024C2, zwcalcar_3=D00024C3.
The parenthesys (unk_D00024C3-unk_D00024C0)=0x3, means the 3rd byte of the array, after zwcalcar_0, i.e. zwcalcar_3.
It is like writing st32.b    [a2]0x3, d15, depending on the version of the disassembler one might use.

to me it looks not like ignition cut, but forcing 0degKW ignition angle in the ignition angle array.

I think this is a second approach, i..e., using ign cut func from DMDZAG etc. I'm talking about your first post which shows how to hijack zwcalcar, it's not clear to me what's holding the rpms at the launch point in that case. My ecu is about the same vintage as MED17.5, it's a MEVD17.2