Anything is possible however if you take a look at the original post here, you will see that the change to 4 weeks is only being considered for the upcoming hardfork because the code change is trivial and low risk:

To implement this change, all that would be needed is to change that number from 13 to 4. Therefore, this change could be implemented without significantly delaying the SMT hardfork ...

Of course it is possible to discuss any other sorts of changes such as configurable power down time, but not within the context of something that is feasible to deploy soon.