This is actually a different issue, most commonly encountered with expression bindings and/or chained bindings (a > b > c > d).
In these scenarios, any transform for d will evaluate as many times as there are links in the chain. This is because each of those properties initializes with an unknown value, then resolves its binding. That property now has a different value, and so any binding observing it will re-evaluate.
We do have a feature in-progress to reduce the thrash these sorts of bindings and transforms encounter, but modifying how bindings resolve is a very involved and delicate process, and there are also some other issues we need to resolve before we can reliably test it.