This worked without having to disable SIP and modify com.apple.airportd.plist
It doesn't take the awdl0 interface down, and I still see some traffic on it, but I can confirm that it disables some awdl features like "Unlock with Watch" and Screen Sharing over awdl. (Screen Sharing will work over your wifi network instead, but normally it'll prefer a direct awdl link)
Wait, why AWDLEnabled = YES? Is it like with those Cisco routers, where "do X" was usually done by negating "do inverse-of-X"? E.g. "no interface up foo" to bring down interface "foo".
Yes, Bonjour name resolution, which Screen Sharing uses, can also run over AWDL, but of course it does not have to.
There was a bug in OS X Yosemite and older versions of iOS which caused any AWDL activity to severely increase network jitter and latency; this sounds like a regression.
Or you could create a kext (using deprecated KPIs) that continuously blocks the interface from coming up: