I am new to Clarity so I certainly won't try and armchair problem solve, but I did spend years of my former life troubleshooting software. I would caution against assuming that everyone is experiencing the same issue. I'm not saying anyone is but it's easy to do, I certainly did it myself many times. One thing I learned is that if someone says "I have the exact same problem" it probably wasn't. There is usually one or maybe two problems with fairly specific symptoms, and a handful of people who have that specific problem. Then a bunch of other people who have similar but slightly differing symptoms. Often those people only see the "problem" once or occasionally which means they probably have something else going on, either a different cause/effect that can sometimes happen, or a mysterious to us but expected behavior, or the occasional "glitch" that computers like to do just to remind us that they are in charge.
Reading through these posts it seems there are a few people who clearly have a problem, they have a set driving routine that in the past was almost
ICE free for much of it, and now on a persistent and consistent basis ICE runs for long and unexplained periods of time. I would recommend continue to concentrate on those people (as you seem to be doing already) and put on a shelf for now seemingly similar symptoms that others (or even everyone) experiences on occasion, as those may be unrelated as similar as they seem.
Even among the persistent there may be differences, which could mean there are two or more different problems, or it could be that the same problem manifests differently. I am interested in ClarityBill's "SOC chasing" theory. I like theories that be proven or disproven, as either result helps move the ball down the field. The theory is that the computer fixates on a particular SOC and is determined to maintain that SOC even though you are not in HV mode. Perhaps the erroneous target SOC is not the same on each trip, but the consistent symptom would be that it seems to chase an SOC. If people with the problem could watch for that, if one or more people find that to be true at least much of the time that would help isolate what is going on, at least for some people.
Tim66 seems to experience that it is clearly related to going past the detent. That could be a clue, assuming Tim66 uses Normal or Sport mode, maybe those in Eco mode could try Sport mode and see if going past the detent causes the problem. Maybe Tim66 can check if he exhibits SOC chasing, which may take several trips to determine. The more data the better. Or maybe Tim66 has a different problem that happens to have similar symptoms.
I am also interested if clearing memory by disconnecting 12V fixes the problem even temporarily for some or most of the people with persistent problems. If it does fix it even temporarily that points to data that is somehow getting corrupted. A software bug would still be the root cause but it helps programmers tremendously if they know that the problem is in the data.
I hope I am not muddying the waters, I don't want to add complication, just some things to think about as you sort through a maze of various symptoms and try and piece together a coherent description of the problem(s).
