WinPE 3.1 supports 802.1x authentication and wifi.
Go through this first.
http://pcloadletter.co.uk/2011/12/03/windows-pe-builder-script-for-waik-including-wifi-support/
then mount the wim and add the packages in the next url and create the lang.ini file
http://www.adamb.com/?cat=7
After building the wim mount it and rename setup.exe to "setup.exe~" so that when you boot the wim it will land at a command prompt.
Boot up the wim, execute the wifi.cmd built in the first url link which is located in x:\windows\system32 and connect to your network.
To start a WDS deployment there is another copy of setup.exe in the sources folder so you can do something like.
x:\sources\setup.exe /wds /wdsdiscover /wdsserver:XXXXXX /unattend:xxxxxxx
I was using an 802.1x auth wifi network (WPA2 enterprise) with a computer certificate method imported from an xml
Suprising overall deployment performance was quite reasonable, on a wireless N connection it only increased the deployment time from booting into winpe to win 7 sysprep of 40 minutes on a wired client to 70 minutes via wifi for a 30Gig wim image.
Whilst this will bypass MDT you can use the setupcomplete.cmd in your install image to finish customizing your image such as join a domain etc.