Bad news sadly: My laptop was leaking memory again of dwm.exe process while I just had 2 video streams open and the memory was leaking around 2mb/s linear growing. I had woke up the laptop from hibernate that day, which is the first time I had used hibernate since the change of the gpu schedule option. So the issue sadly is not connected with the gpu schedule option it seems, but rather using hibernatemaybe. I had a auto hibernate timer of around 10h set, so when I would wake up the laptop quicker, it wouldn't trigger hibernate. Someone maybe can confirm, who had the issue also used hibernate in between? Thats also maybe the reason why Intel couldn't reproduce it, because they never thought of using hibernate for the testing.
also if you are using "fast startup" that basically means it will use a "mini hibernate" (mini hibernate of kernel + drivers + system related stuff) each restart of windows, so if hibernate is indeed a root cause of this issue, it might trigger it too with "fast startup" activated.
you can deactivate hibernate, which then automatically turns off "fast startup" by opening a cmd.exe as administrator and type in: powercfg -h off