Solving this would be helpful for teaching and I think it's not trivial to do well. I think there's an argument that being good at troubleshooting and debugging is 90% of programming so the shitty dev environment setup currently is a bit of a filter, but I generally think that's a bad status quo rationalization.
All this is to say - I think there's a market and the product is likely valuable, but I also don't think it's reusable rockets or rebuilding the internet or the 'most ambitious software company in history'. This kind of framing turns me off and when paired with stuff like this post leads me to avoid the company entirely.
https://news.ycombinator.com/item?id=9224
Building a better UX isn't done 'simply' - and the result is often worth billions.
I would consider an approachable wrapper over a difficult tool to be innovative. Programming languages are essentially just UX wrappers over assembly. Is garbage collection an innovation, or a UX improvement? What about type systems? None of them make things possible that weren't possible before, they just make it easier.
Information for the sake of information is interesting, but where is it's value if it can't be applied to anything?