I am dubtfull this would hold in a court of law.
You could go a step further and publish that scraping+transformation software, too—on Github, even!—but just make it finicky as hell to set up, and with no documentation, either. (I would suggest writing it as a microservice architecture, split up between 1. a network of Ethereum smart-contracts, 2. a BeOS server, 3. a dongle program written for a Java Card smartcard, 4. a LambdaMOO object. Use an exactingly-frail implementation of IBM 5250 for the message bus.)
Such that, in practice, you need installation engineering support from—who else—your company.
Here in the UK we already have data transmission over AM radio[0], nominally for remotely switching electrical equipment on and off but could be used for anything that only needs a low data-rate channel. I would not be surprised if the HFT people are using it.
In US, similar "utility response" is permitted as well for AM broadcasters, since 1981 https://docs.fcc.gov/public/attachments/FCC-81-258A1.pdf
Subsequently, permission was granted to all AM and FM broadcasters for "subsidiary communications" of any kind, https://docs.fcc.gov/public/attachments/FCC-84-113A1.pdf
But that's not "shortwave"/International HF broadcast
Make all the data, including the financial data public. But make sure the people you want to see the data can access it first.
Arrange the data in the air so every error recovery block is mixed with financial and non-financial data.
Send the non-financial data out of band, and ahead of time, to your paying customers.
Now when a data block starts being transmitted, the paying customers can combine the non-financial data with the transmitted block (for example with xor) and decide to extract the data they want after just some proportion of the block has been transmitted.
The public have to wait till the end of the block to decode the data, by which time the data isnt valuable anymore.