The section "FORBID CONSTRUCTS THAT LEAD TO FALSE RESULTS" perfectly summarizes the Elm community: "my tool is smarter than you, so it will tell you how to bend your code so that it understands it"
This advice was for custom rules for a team, so it's about enforcing what the team has already agreed upon and understood the trade-offs, not anything the tool decided upon on its own and imposes on the team.