Strange anomalies when UEFI PXE-booting

Hey first of all some insight:

WDS and MDT on same server, no DHCP scope or IP helpers since we have a strict VLAN for installation. MDT version 6.3.8450, ADK 1903 (fix applied), Win-PE addons 10.1.18

Story so far:

At some point our 1909 deployments started to fail with booting after OS deployment, all seemed normal but MSR partition was unhealthy. Since no one acknowledged any changes in that server I thought I'll just rather import OS again and regenerate new bootimage just in case.

Now we can UEFI PXE-boot and install BUT if for some reason installation gets cancelled or cut of for some reason, it just won't PXE boot anymore.

Scenario: After failed OS install start computer and hit f12 for ipv4 boot, it get's server response and IP, it loads the file and errors out to 0xc0000225 Workaround for that is to usb boot to recovery and delete existing partitions and voila, machine pxe boots again

If anyone has ANY ideas what to try, I'm all ears since this has been a nightmare for the past 5 days.

EDIT: So...

After long days of pulling hair and praying to any higher force I have found out:

If I choose to install anything from "roles and features" under custom tasks, it only finishes successfully if take off secure boot. This is nowhere near what we want to accomplish.

If I disable "roles and features" step I can add pretty much anything to task sequence and it finishes nicely without any problems.

This is not the case when installing 1809 windows 10 with uefi and secure boot, works flawlessly there.

Anyway since we have most likely accepted that outcome I would just ask in the if anyone has something what could overwrite ongoing deployment so leftover junk from failed one wouldn't stop starting a new one?