You have confused TWO ENTIRELY different posters. The OP states his theory and how he tested it for confirmation. Someone then came alone and said, "OK how do I avoid the bug and then show that the iPhone 4S actually works".
So to help explain what is going on lets start with a level playing field by breaking down only the first post.
it seems that the very cause of battery drainage is a bug in the video card driver , which could be triggered by applications making use of certain iOS APIs.
I found this by looking at the energy consumption graphs extracted from my iPhone 4S and comparing them with other information taken from the device.
Now iOS is a *nix based operating system. Which means it has a video card driver as part of its core components. This driver is in control of a GPU. The key part to this is that the GPU can run code, on its own internally, with NO help or need of the CPUs interaction. That is why they are now called Graphic Processing Units. Since no one has been able to figure out exactly what is going on, this explanation has become the Occam's Razor in a sense. No one could pin down an exact cause because so many apps helped exhibit the bad behavior. That means they must share a common result. The ability to change something that gets stuck and continues to drain the battery.
Now I already stated that I could play games while the phone is at 100% charge and then force the phone to fall below 96% and never be able to recharge 100%. Those games where utilizing the GPU at 100% power. Other have stated they saw this behavior without ever playing a game. The theory he posts explains BOTH conditions flawlessly.
The second poster then asks the obvious question, how do I avoid the GPU at ALL COSTS to see if I can get a battery drain that is better than 1 to 2% per hour. He did it by killing off all code that could possible cause the GPU to keep running code after the fact. His test results show the battery drain is now at 1% per 3 hours. A full 300% increase in battery life. And all he did was AVOID the condition the OP stated was the issue.
As far as I am concerned this looks like the real deal. I have stated MANY times that this was an API issue with a new section of the hardware. It fits and it looks to be reproducible. I figure by next week this result will either be proven beyond a shadow of a doubt or it will lead to the exact root cause. Either way, it was bloody brilliant work.