Fair enough. With MEB 2014, I sent genuitec a few nastygrams over their decision to punt on SVN support. I'm there with you. But I did get it to work well and you can always use Tortoise--that's what my team uses. Do you do a commit every 15 minutes?
As for your troubles with WebSphere--well, that pig is something I have been able to jettison many times for all the alternatives so if you're still stuck with WebSphere you have your own set of problems.
Also, frankly, I think you are being sandbagged if people can claim that 25% of their time daily is waiting for MEB. I think, frankly, that has to be bullshit--they are exaggerating.
Also, if you have to leave MEB, then there is the fabulous free Spring Tool Suite which does lots of what MEB does. I understand that, technically, .NET can connect to any database vendor's driver. But you also know that when you're in a MS shop you end up--because of support and tools such a VS--end up being a 100% MS shop. It just happens. I doubt MSDN is going to give you oodles of pointers on how to configure .NET and solve esoteric problems on Postgres, MySQL or Oracle. It's not in their best interest to support the competition. So, bottom line, the decision to become an MS shop is a higher cost point and so fewer and fewer shops are choosing that. I look back on my decision in 1999 to become a Java fiend as the best decision I ever made and I stand by that assessment to this day. The last product I worked professionally on that came from Microsoft was VB6 and it constantly fucked up. Certainly, your mileage may vary but I have found my salary spiraling up and up without end because I know Java and the JEE ecosystem and its many open-sourced brethren so well.