[...]The other thing is the metrics; they put out heat maps on where people died, how often they died, how often they got attacked, how often Scratch got petted, ect.
Odds are they see players repeatedly loading to pass a check. If enough people do it enough times, someone is going to suggest they just save people time, skip at some least some reloads, and make things easier.
I hope the devs wouldn't listen to that person, at least blindly/using only that reasoning. People reloading a save to re-attempt something doesn't mean they dislike the original difficulty of the thing, especially for an EA game where we're explicitly here to test out everything.
E.g., if there's an optional but incredibly difficult encounter, you're going to see a lot of reloads from people dying it and then trying again. Now, maybe the encounter is too difficult. But maybe it's at a good level of difficulty, and lowering that difficulty to prevent people from needing to reload just makes the encounter less noteworthy as there's no longer a sense of accomplishment from beating it.
In this specific case, in addition to being a hard fight that challenge-seekers might want, the MF eating your brain is a good teachable moment: doing dangerous things can have consequences.
The problem is that most criticism around Arabela is lack of satisfying options after you fail persuating Kagha ... if Larian indeed just lowered dificiulty roll for persuating Kagha so not so many people have to see poor Arabela die, the problem remain intact ... its just not as obvious, since not so many people see it.

I hope this isnt Larian way to fix things. :-/
+1 More, not easier, options please.
I've previously suggested that if you fail that persuasion check, you can still notice the intent of the snake to attack (maybe requiring a perception/insight/nature/animal handling check). Then you have the choice to:
- step in between the snake and Arabela, taking the hit
- pre-emptively attack the snake, angering Kagha
- keep trying to persuade Kagha, in which case the snake attacks Arabela
Basically, fail forward. Failing shouldn't strictly remove content, but provide different options for new content (with possibly more consequences).