CWKPQ!

I ignored that statement the first time around because I thought everyone would unanimously treat it in the same manner, apparently I was wrong.

In my opinion, CWKPQ isn't that good. Even in the old days, it was already becoming ridiculously easy compared to the effort to get enough people to actually go in, the most mundane, average people you can think of.

God knows how long ago that was. We went through Big Bang, Chaos, Legends (lolDS) with craploads of skill revamps, had potential and crafting which means an easy 20%+ mainStat for just about everyone, mass duping that most of the population had to benefit from in one way or another.
In fact, I would be quite surprised if my weaksauce DK can't solo the entire boss stage, and I scroll/pot/cube my own pomegranate without ever stepping into the FM since ages ago.

It's unbalanced in the context of the horrifically broken things Nexon has done to the game in the past couple of years. And it's still some of the best designed content in the game.

I don't care if you can solo the bosses in CWKPQ, I care that you can do your room and arrive on time. The requirements of the pq itself are the perfect foil for the overfunded jackasses who think soloing is a solution to all their inadequacies. You cant solo your way to 10 signups, or 5 completed class specific rooms. You can't solo the organizer's directions.

CWKPQ needs to be fixed only to the extent the rest of the game was broken.

I believe it was their attempts to make it more of a challenge that introduced the channel-crashing bug.
They closed it off "temporarily" with the intention of finding and fixing the bug real-soon-now, but were never given time to look at it.
Finally, someone there must have gotten as frustrated as the players, and said, "Let's just put it back the way it was, for now. It will be too easy, but then the entire game is too easy. When we get time to fix that bug we can release a 'revamp'."

It's possible, but considering the bulk of Nexon's work is localizing KMS's big patches, I doubt they were simultaneously taking the initiative to make creative changes to content. What most likely happened is one of the many GMS specific code nuances they had been using in CWKPQ conflicted with something chaos changed to MS at large - and that caused channel crashes.