I halfed it and there is still a slight delay, but I haven't had a chance to really play with it further.

I don't see a problem with reducing/zeroing it.

I'm pretty sure zero would be deactivated and that it is CPU time not seconds.

I see the same as you in my R box (0x3333), scale=1, offset=1

the others are 0xffff

$ grep ZKLAMFAW *.csv
4Z7907551R.csv:"ZKLAMFAW","0x1edac","Zeitkonstante Filterung Anfettung durch Fahrerwunsch","1x1","16 Bit (LoHi)","-","s","-","-","1.0","1.0","1.0","13107.0","13107.0","0x3333","0x3333"
8D0907551F.csv:"ZKLAMFAW","0x1ca4c","Zeitkonstante Filterung Anfettung durch Fahrerwunsch","1x1","16 Bit (LoHi)","-","s","-","-","1.0","1.0","1.0","65535.0","65535.0","0xffff","0xffff"
8D0907551G.csv:"ZKLAMFAW","0x1c3f0","Zeitkonstante Filterung Anfettung durch Fahrerwunsch","1x1","16 Bit (LoHi)","-","s","-","-","1.0","1.0","1.0","65535.0","65535.0","0xffff","0xffff"

Something is screwy here.

What boxes use CWLAMFAW=1 by default?  We should look for our ZKLAMFAW from such a default box as seen from the factory.

Doc Brown does maf real gud.

I think it's pretty bad for fuel economy.
Only place where you want enrichment through LAMFA is WOT really, run rest at lambda=1 and set BTS correctly so it takes care of EGT's at 3/4 throttle for example.

Otherwise you will just have horrid fuel economy, even when driving normally.

I agreed. I only modify the WOT line