The reason we ask people to remove plugins is to find out which one is causing the CTD. That's just the first step. Once we find out which plugin is the problem, Saso then tries to figure out a way to create a "workaround" to the problem, if he can, from the TBM side...so in the next update, the conflicts will hopefully stop. If he cannot find the problem in the TBM, then we ask the person with the problem to make contact with the developer of the plugin so THEY can take a look and see if they can find the problem.
The same thing happened with the Saab. People were getting crashes when they ran the Saab with xEnviro, and they were absolutely sure it was the Saab that was at fault. Jim (Saab programmer) and Ben (Gizmo programmer) went through every single bit of code to see if they could find the problem. They never did, and determined it was indeed, xEnviro. Andrey at xEnviro denied there was any problems. I pleaded with him to check, and he reluctantly checked, expecting to find nothing. He added some debug code and asked a small group of people to test it. After testing, he found the problem was indeed with xEnviro and proceeded to implement an update. This update, however, from my understanding, won't be available until version 1.10.
We certainly don't want anyone to permanently remove their plugins. It's just a way for us to determine what is causing the problem so we can go about fixing it.
In saying all that, most of the issues people are experiencing are isolated to a very small group of people, but we still try to help as many people as we can.