Yeah, it's a really tough balance to strike. I've worked with teams and systems where they were fully happy to apply a hack and move on and it worked great for them. I've also worked with teams who had a terribly bad culture of throwing shit at the wall to see what sticks for fixing weird errors and in the process making problems worse without actually fixing the problem.

Using good judgment to figure out when a hard RCA is necessary and when it's not is key to making forward progress without constantly shooting yourself (or your teammates) in the foot.