If this was a conscious process, that is taking solutions from mainframe, analyzing them and deciding to use some of them also analyzing the knowledge,pitfalls, problems and experiences from the past and incorporating them into the new tech then this would be a good thing.

However if this is done through a simple reinventing the wheel route, there is a high chance of hitting the same walls and repeating the same mistakes.

This is kind of similiar to a "let's rewrite this code from scratch in new shiny lang/lib/framework" with the expectation that new code will be bug-free from the start. It's not always bad, it is sometimes necessary or it may turn out to be more effective than trying to fix bloated code. But very often the new code has problems exactly the same as previous code and effectively the developers reinvent the wheel multiple times in the process of rewriting.

I am not sure if you're following the github spec repos, but at least check them out. I really don't think these people are reinventing the wheel badly. The last 3 years have been full of discussion about every single detail, including behavior of various different prior art, host platforms, hosted platforms, etc. These discussions are public, why don't you join if you can help? Even a short list of "look here" would be a great help.