This is why good developers are hard to find. There aren't a whole lot of developers who have the required technical abilities while also being able to communicate with clients/leadership effectively.
The CEO is doing that because they don't understand how things work in your org. If you're the one communicating with the CEO, then its your job to be persuasive when telling them why what they're asking can't happen the way they're envisioning.
If they come back with "make it happen" then you weren't persuasive enough.
Good luck getting your organization to support building two apps. And even if you succeed once, good luck getting your organization to ship features twice every single time they want to build something.
What will end up happening is you have your normal app which isn't accessible, and a second app with a fraction of your features that is likely often broken because it's hard to prioritize.
> You don’t think the steady erosion in system reliability and ever increasing outages is unrelated to these pressures do you?
Outages have steadily decreased at major companies. I don't know what you're looking at.
Remember AWS taking out a good chunk of the internet many times a year because their east coast data center kept going down? Remember the fail whale meme-ing because Twitter was so unstable?
Industry site reliability has only gotten better over the years.
You're in a bit of a bubble. This is not the case for the majority of jobs.