Quote

Have you received some feeback from a Core Developer, or from someone who is not a pleb?

I guess not. All changes described in the whitepaper from this topic are backward-incompatible, that would mean a hard fork (or an altcoin, if it would be based on its own Genesis Block). But even in a soft fork case I doubt miners will go for it. They have no reason to split the whole process into two phases. It will be just another obfuscated Proof of Work, where things are the same like in plain, old, single-phase Proof of Work, but only some people will know how to produce the best blocks.

Or even worse: if it would be backward-compatible, then it could be simplified as just another merge-mined coin: by producing coins valid in both chains, miners will never switch to your coin, they would just get the same amount of Bitcoins and YourCoins, then sell YourCoins for Bitcoins, so the price will fall. I guess the same things would happen as for example in Luck: first some discussions on bitcointalk, then some negative feedback, then some test version release without addressing any problems from that feedback, and then creating just another altcoin that would be pumped and dumped as usual.

Quote

So, it will reduce the miners business cost and increase their profit.
The mining cartel will make more money with less running cost.

It would be true only for a short period of time. Then, the difficulty will adjust. Miners can switch between Bitcoin and your coin, also they will probably sell everything when your coin will enter some exchange for the first time.

Quote

Plus no offense to you, but how can we know that your proposal isn’t like the Space Ghost meme that says, “I am new to Bitcoin, and I am here to fix it”?

It probably is. But when people don't want to learn from mistakes made by others, then they have to make their own.

Quote

Be cool baby. Things will come in their due time. Stay tuned.

Satoshi first did a lot of coding and testing, and then wrote the whitepaper. I think in many coins, things are going backwards: first there is some unchecked idea with some whitepaper, then there is some coding and testing, and later there are many big surprises, because some things were not checked before releasing the whitepaper and they are getting out of control.