Well, you know, nothing ventured nothing gained. So kudos for starting a tough conversation. What you say is true about delegations. The delagatees aren't going to want time limits on those. Personally, I like the idea of being able to, as delegator, choose when my delegation is removed. A time constraint could take that away. And, seriously, that aspect of your proposal is much less disruptive and probably less influential on the outcome you're looking for than other aspects of it are.
I'm convinced the only real protection against centralization of power is pure decentralization. Hive can't achieve that with DPOS. The fact that there are witnesses who are voted in by the rest of us means that there is less decentralization than we're all comfortable with. And I can't bear to think how many inactive accounts have active witness votes that may never expire because account owners are nowhere to be found. If you want to spark real change, how about a time limit on witness votes? What if they expired after three years, or expired after an account holder had no on-chain activity in one year?
I still think a longer duration time of power down is a wise move. If you want to reduce it, I'd be more comfortable with 7-10 weeks.
Good point on the multiple posts. It probably is best to lay it out all there and get the conversation going.
RE: Hive5 - IDEAS for Public, Witness & Dev consideration v1.2.1