I feel that the "best practice" of consistency is not advocated for in software engineering. Like theory in all fields, in software engineering we're prone to idealizing systems, acting as if it's always better to break bad patterns ignoring the overhead the inconsistency causes. Sometimes it's better to have four equally worn tires that you'll replace all at once, than three worn tires and a random brand new one.