Not sure I understand this, isn't the device just a low-cost implementation of a DIAL device? http://www.dial-multiscreen.org
Honestly, it's really silly since the built-in Chrome casting webapp is basically "throw arbitrary content at the screen via WebRTC" -- so hypothetically you could write a local WebRTC client that pushed your local video content to the device (and sidestep any whitelist restrictions). Unfortunately, WebRTC looks like a needlessly complicated protocol to implement.