First of all, this is a classic performance-friendly way to simulate wiggly motion (often used for things like hair or tails where bones are connected in a chain，like https://www.youtube.com/watch?v=tQV_wPQ8rBk). I simply turned it into an add-on to save the manual steps. The dependencies always flow downward along the bone hierarchy – no constraint points back to a parent bone or any bone higher up the chain. Unless someone deliberately adds reverse constraints, a dependency cycle will not occur.
Isn't this creating a dependency loop? If so, it should not be approved for listing.