I'm not aware of one, but you're welcome to jump in and write one ;). It shouldn't actually be too tough, and I know the guys who run our GitHub repo (on the DSC Hub tab here) would likely be willing to help out if you get stuck.
Implementing that resource seems easy enough, but defining its use cases might be a bit tricky... should the DSC engine wait for the BITS transfer to complete before it returns from the Set-TargetResource? Or is it enough to kick off the asynchronous BITS job and allow the rest of the configuration to process? (Which would mean that the rest of the configuration cannot assume that the file transfer is done.) Most likely, both scenarios should be supported, with the behavior controlled by a parameter to the resource.
If it's asynchronous, then the Test-TargetResource and/or Set-TargetResource functions would need to be smart enough to detect that a copy job for the file is already in progress, and not create a new one.