Thanks very much for the feedback! This underlines quite well why it makes sense to keep the tool configurable, because every situation is a bit different (new code / legacy code, requirements to downport, team preferences etc.).
Regarding "religious" cleanup rules :-), even those could make the code more readable if they make its syntax and appearance more consistent; but nobody will be offended if you deactivate such rules!
"Remove long IF blocks at method end" might depend on configuration ("Replace IF blocks with at least ### lines"). There are legacy code methods out there with IF blocks spanning hundreds of code lines… on the other hand, the cleanup rule somewhat goes against the principles of structured programming (which demands a method to have exactly one entry point and one exit point).
"Use FINAL for immutable variables" is actually deactivated by default, because this keyword is rather new to ABAP, so it may only make sense on new code that does not need to be downported. Since this is always only local (inside of a method), it would be easy to change if the respective method needs to be enhanced later. And the rule has a careful approach, so, whenever a reference is created to a variable (which could be passed on to another method etc.), FINAL will not be introduced (see the examples of this rule).
Anyway, thanks for your thoughts, and as you can see on the issues in the ABAP cleaner repository, new suggestions always come with some discussion until good defaults and configuration options are found to address the various needs!
