I don't think statements that KC had a bad line are totally accurate. If you have an excellent run game, and a guy like Cassel takes less than 30 sacks, you're doing something right. Remember, Cassel got sacked a league leading 47 times when he started for us. He's one of those guys like Roetlisberger and Vick who's game translates to a lot of sacks.
NFL.com - Offensive Line Stats
That shows that KC, who had the arguably the best running game in the league, had most of their luck on the left side and up the middle, which speaks well of Waters.
Brian Waters stats - STATS Hosted Solution
That link tracks Waters sacks allowed (.75, excellent) and penalties (2 for 15 yards, also excellent) from last year. Statistically, it's easy to see why he went to the Pro Bowl. Reports seem to suggest he's still an excellent pass blocker, but he's fallen off a little as a run blocker. Considering the type of team we are, that's okay with me. If his poor run blocking limits our run game to only being as good as KC's, I can live with that too.
As for getting cut by KC... obviously, it doesn't bode well. But he's vocally wanted out for a long time, and they really wanted to get his replacement on the field (Jon Asamoah, drafted 68th overall in 2010). In the end, I think he was the best option out there for our situation. If he proves an upgrade from Connolly, then that's amazing. If not, he's a fine place holder.