A bit more context around the issue, now that the proposal has been adopted.
Earlier today we got an alert from our monitoring stack that an unexpected behavior has been encountered and we tracked it down to the recently added functionality:
Without disabling this functionality in some edge cases it might come to consensus stalling, and requiring subnet recovery.
The reason we introduced this functionality in the first place is mostly around Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months and the related node redeployments.
The need to go through the NNS proposals for these node redeployments significantly increases the friction and worsens the UX for node providers.
So we will give our best to re-enable the functionality as soon as possible.