A little chip that can read analogic OR digital IO and securely send over via radio seems to me like a very standard, reusable and useful piece of hardware.
It is something that you can sell to pretty much every industry, so you have a lot of scale to leverage.
I do understand that, if your application need to read temperature and send it over you will design the whole chip together, but when your application need to read also humidity and send it over I believe that you can reuse the design of the old chip; so, over the years, a standard way to read from IO and send over secure radio connection should emerge.
The problem is that on its own, that isn't a saleable product, everyone who has a need for that would be able to make it cheaper if integrated into their product as-a-whole. Integration is everything.
Because some markets like the industrial market - will be willing to pay a bit more for that.
What people never seem to realise about embedded s/w is that these devices are only cheap (and hence viable as products) when produced in many thousands/millions... Because of this, the bill-of-materials overrides any other concerns so you end up picking the smallest/cheapest possible device you can and do your utmost to make it work.
This means you need to be intimately familiar with the low-level aspects to be able to optimise your code to the hardware. The best you can say about these environments are that they are for "rapid-development". no one would ever take a design created in one of these type of environments (Arduino included) and make a viable product from it unless cost was not an issue, which is never the case in the embedded world.
So, in answer to your question, it is all possible... apart from the 'cheap-as-chips' part unless you opt for traditional low-level embedded s/w design.