SOLVED: DKOMBI2 CAFD Corrupting after car sleep

[bavees]

Greetings!

As per the title, I have a very strange issue with the DKOMBI2 on my 2017 G30. The car was originally equipped with 6WB from factory so no retrofits done.

I bought the car with the alpina display enabled but wanted to revert back to stock. Got Esys 3.35 and Esys Plus with full data.
I edited the cafd and disabled alpina display and everything worked OK. I later decided do dig into some more customization options (disabling the vehicle check and brake fluid service display + making the sport gauges gray). 
All worked fine as well. Then decided I want to try to the alpina display again, went back to do it. Coding went OK display changed. I left the car and went to work. When I got back to unlock it some hours later the cafd was corrupted.
And now I'm stuck with the cafd re-corrupting each time the car sleeps. I have tried every method I can think of to fix it but it wont stick.

I tried to modify my SVT and recode to factory.
I tried to dedect cafd for swe and inject it that way.
I also tried to modify svt_ist and before calculating svt_sol to trick a rewrite of btld,sfwl and cafd via TAL processing.

In each case the behavior of the cluster is the same. I can re-read SVT after doing the coding and the correct cafd will show. But as soon as I lock the car and let it sleep (or force a DKOMBI reboot via esys) the cafd gets corrupted again.

ps: I also tried all of the above steps with esys 3.30, 3.34 and 3.35 both with and without launchers.

I have tried to do the coding with a connected battery charger, even with the engine running to ensure stable power to the battery. Also tried to buy and register a brand new battery but nothing helps. cafd will still get corrupted after car sleeps.

Alongside with this I started to get an issue where my vehicle inspection will say it expired on 11/2021 and regardless of what date I set it to both via idrive and tool32 it will still re-expire to the same 11/2021 date. I even tried to disable it via ista+ and it re-enables with an expired date of 11/2021 on its own.

It really seems something with the memory of my cluster is going bad and it wont allow data to be permanently stored into it.

All other car systems remain unaffected and problem free. I have also tried to code stuff to BDC2 and HU and they work fine. The issue happens only with the cluster. 

At this point I'm open to any ideas and suggestions as I'm starting to lean towards buying a virginized unit and replacing mine but would ideally like to avoid that cost.

Thank you in advance!

edit:
forgot to specify the full psdzdata I have is 4.53.41
and for esys 3.30 I use launcher pro 2.8.1.155
for 3.34/3/35 i use esys plus 3.8.1