Yes — from a high-level review, this looks feasible and reasonably straightforward for the dev side, but not completely trivial.
The change is fairly well-scoped around the distribution module (staking rewards flow) and app wiring. It would likely involve modifying the reward withdrawal logic, enabling burn permissions for the module account, and ensuring the “once per transaction” rule is enforced safely.
That said, since this touches consensus-critical logic, it would require careful handling of:
exact trigger point (which reward claim messages are affected)
enforcing 1 burn per transaction deterministically
failure behavior (e.g., insufficient balance for burn)
upgrade handling and backward compatibility
proper testing to avoid unintended side effects
Overall, it does not appear to require major architectural changes — more of a targeted protocol-level adjustment — but still needs proper review and implementation discipline.
Would it make sense to move forward and formalize this into a full governance text proposal for discussion?