They are not the same thing. The oen you refeer to is a way to call python inside mael well, its not realy usefull. And i agree that is surely cartered by mel forum.
Its not enoughth to expose maya to python python needs to be exposed to the api. THeres no siginficant gain of making a python MEL communicator. Its still going to have all flaws of mel but hidden under a interface thats not telling you why it dont work.
I know its not ready but ist strating to be python will only be usefull once its is API level connected in a way thet makes the api work PYTHONICALY. Now the other solution is actualy MUCH harder to do. But actualy usefull. Thet means your going to be making bytecode that RUNS like a dll. NOt like the other, and much unlike mel.
Now the newer actualy makes sense, it does not expose maya to python calling it exposes PYTHON for caaling maya maya calling trough API interfaces. It swaps the C++ api for pythoon wich makes sense. And therefore its PURE python and has no bearing on mel.
Its like saying windowshopping and going shopping is a the same thing. BUt adding now might be a bit premature i agree.