RE: 2 Year Terms 
As a current member of the security council and an active delegate that I haven’t experienced fatigue with yearly votes. That said, I don’t see any issue with moving to a 2 year term as long as people can resign. I also don’t mind a 1 year term, it really doesn’t matter, but I mildly support 2 year terms as it reduces operational overhead.
RE: Reduce qualification threshold 
I don’t support reducing qualifications. I don’t see why we would make th upfront filter weaker. Requiring 0.2% of the votable ARB supply, (around 8 to 9 million ARB), feels right. If someone can’t reach that in the nomination phase, they won’t make it as a member anyway. With 6 seats and around ~200 million ARB on average participating, it should be fine…
Presented another way, looking at the current top delegates:
With a 0.2% voting threshold, Entropy can make almost 3 full nominations, L2beat and LobbyFi can make almost 2 and Gauntlet can make 1.5 nominations
If we halve the requirement, then Entropy can make almost 6 full nominations, L2beat and LobbyFi can make almost 4 and Gauntlet can make 3 nominations…
Which sounds better? To me it’s an obvious choice, so i don’t support this change.
RE: Bypassing Nominee Selection
As a current member I am naturally biased, but allowing sitting members to bypass the nomination phase makes sense to me. If you’re already in, and you want to do it again, you’ll almost certainly clear nominations anyway, so forcing it just wastes time. I’m confident no current member would have trouble passing the filter, so why make them jump through the hoops?
RE: Key Rotation for Candidates & Key Rotation for members
Key rotation is obviously critical for members of a 9/12 multisig. People can lose access to their keys in a multitude of ways so having an easy way to fix this issue is a no brainer… but allowing candidates to rotate extra keys feels like unnecessary overhead. Just let members rotate their own keys, nothing more. It is a 9 of 12 multisig, one wrong key for a day doesn’t break it. Adding complexity for the small period where a candidate needs to change their key seems like needless scope that adds needless risks of bugs or exploits. I would suggest to keep it simple, only members can rotate out of their keys, the function for candidates is needless overhead as we can use the fact that members can rotate to address the issue.