Why are you looking past it - that is a point that is integral to any discussion of automation.

Currently, using pre-recorded x,y coordinates (a function not supported by the default UI at all), to target or cast a spell is functionality outside of our Terms of Use.

I would strongly advise shying away from this program, if it is causing mouse moves (even simulated mouse moves) to occur in response to user inputs.

Mouse moves are the purview of the user, not a program.
I still believe mouse broadcasting is okay, as long as you're actually moving the main mouse, no pre-recording. The whole one action equals one action idea comes to mind here.
Although "user inputs" could be anything.

The biggest thing for me is not having mouse movements be pre-recorded.