No. That in itself shouldn't be a cause for concern. Local users can do anything to their own machines already. It would be a concern if you persist this to then later be loaded by someono else's machine.
How will this work with aviation? I know it probably won't affect most IFR flights, but still possibly dangerous for VFR. Will there need to be a new restricted area for each deployment?
Depending on the altitude, they could keep these within class G airspace, which means VFR's job is to see and avoid. I think that's a pretty defensible solution as a pilot who spends all of his time in VFR operating in Class E/G airspace.
A project I did a couple years ago was to have an onboard SDR that communicates automatically with airplanes in the vicinity, or switching to manual where the drone operator can communicate as if they are “on-board” through the internet by a mic on ground. I can see something like this is doable, with a modified system to fit the length flight, after all, the position is fixed so I don’t think it would be a problem.
It wasn’t an ADS-B, Transport Canada (the FAA equivalent in Canada) doesn’t like ADS-B on drones yet, so the solution was to have an SDR (BladeRF, full-duplex for Tx/Rx), the on-board SBC had a server the received the voice sample (either direct through ground station MIC or automated reading directions, alt, etc every X period of time) and then broadcasting it to the airband, so it’s simply:
Ground station mic -> internet -> server on SBC -> SDR -> airband (AM, I think it was ~120Mhz that time) -> other pilots
If you have the manual communication (where the drone pilot comms and not an automated broadcast), you can pretty much talk with pilots as if you are on-board.
I had a better write up if interested on how it works in here, in the “SDR” section.
(my-name "<img src='#' onerror=alert(1) />")