Something like Alomomola, for instance, who performs mostly the same support role as Vaporeon, but uses its Attack statinstead.
Actually, Alo's offenses are both terrible. It's best bet is just to ToxiStall, or use Scald for the Burn chance. Waterfall isn't gonna be hurting anything, but Scald helps Alomomola cripple things like Ferrothorn.
----
My feelings on Drizzle have been stated multiple times, however, this time, I'm going to be explaining something a little different.
Right now, we've already made a complex ban to save Drizzle. Swift Swim + Drizzle.
Anyone who says that banning Kingdra and co was the right solution is likly wrong. This is mainly because Drizzle is borderline broken as it is already. Imagine if it had the likes of Swift Swim Floatzel, and Goyebass as well on top of what it has now?
Then there's the issue of how far we have to go to save Drizzle, to me, it's seeming like 4th Gen Mence all over again. Scizor was everywhere to deal with Mence. Sand is everywhere, and teams that don't run sand run Ferrothorn or Virizion, two of the very few checks to Drizzle teams. Many Sand teams have started running Rotom-W with Thunder, from my observations. Thunder Rotom-W is kinda useless in the Sand...
I mean, look at what Drizzle does:
It undoubtedly breaks Kingdra and Manaphy
It probobly breaks Ludicolo and Kabutops
It might break several other Swift Swimmers
It makes Thunderus more broken
It makes Rotom-W a juggernaught
It makes CB Azumarill obliterate literally anything that dosen't resist Water or have Skarmory-like defenses
It makes Ferrothorn even more inpregnable
It makes Fire-type attacks less viable in the metagame
It gives many pokemon who use Water as a coverage move more power, such as Latios and Hydregion [He can use Surf, belive it or not]
It allows Hurricane Spam from Tornadus and Dragonite [And other non-viable pokemon]
It makes Rain Stall possible.
---
So far to save Drizzle, we have:
Implemented a Complex ban, which has opened the floodgates for things like Ability + Pokemon bans.
Banned Manaphy
Even after this, Drizzle got a 31 - 39 vote to ban it, which may range from 37-39 to 31-45, with even the most pro-Drizzle vote possible hardly being resounding [Not even 66%, which, bear in mind is what you need to auto-ban something]
We may be banning Thunderous [Although the degree this is Drizzle's Fault varies, but Thunderus benifits from Thunder, and from more Waters in the metagame <_<]
-------------
Also, on the topic of stopping things being re-nominated, I propose this, since I can't post in PR:
If a Supermajority [66% +] is given to keep a pokemon or Ability at any point, it is unable to be nominated again until the situation changes.
If <33% is too tight, 20% seems a sensible option.
Of course, Abstains would have to be factored in as pro-ban for the purposes of this limit, because Abstain means that the voter hasn't made their mind up, and thus, needs more time to come to a conclusion. Making something impossible to be tested again... defys the reason why those people abstained.