I would recommend to use the UEFI PXE Boot and that any UEFI boot settings on the devices to be deployed have UEFI settings enabled, including the UEFI Network stack (At least on dell devices).
For testing I always run a VM to test my deployments before using on a Desktop and prepare it as much as I can and then deploy it to the devices. It helps to add all the drive packs from the Hardware Manufacturer (Say Dell, HP and so forth).
Dell
https://www.dell.com/support/article/us/en/04/sln312414/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment?lang=en
HP
http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html
http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x86.html
Lenovo
https://support.lenovo.com/us/en/solutions/ht074984
Acer
https://www.acer.com/sccm/
Microsoft
https://docs.microsoft.com/en-us/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices
With Pre-Staging machines you need to rely on adding the device mac addresses manually or use Microsoft AD to add them with a Script or Manually to be ready to WDS. This makes it that you can add the devices before hand and only those devices will get the deployment. However you can setup an specific network or VLAN to have the WDS
For Multicast, I like this article
https://specopssoft.com/blog/wds-multicast-configuration/
However I like the option to disconnect the clients when their speeds go way low and then go unicast instead of multicast. Multicast makes sense that way that way the slow clients do not slow the faster clients.
I am still not sure why MDT is not being implemented but that is for another post.
