Something over-writes my start-up script defined calls to "xinput set-prop" and "synclient [property]=". How can I find out what is causing this?

I am trying to enable synaptics touchpad "natural scrolling" on startup, based on the registry key "EnableNaturalScrolling".

    if [ $ENS -eq 1 ] && [ $VSD -gt 0 ] ; then
             VSD=$(synclient | grep VertScrollDelta | cut -d "=" -f2)
             VS_INVERT=$((VSD * -1))
             TPAD_ID=$(xinput | grep Synaptics | awk '{print $6}' | cut -d "=" -f2)
             xinput set-prop $TPAD_ID "Synaptics Scrolling Distance" $VS_INVERT $VS_INVERT
             synclient VertScrollDelta=$VS_INVERT
    fi

When this condition runs, all values are as expected ($ENS=1, $VSD=112, VS_INVERT=-112, TPAD_ID is what I need it to be)

The last two commands are two separate ways of enabling "natural scrolling on a Synaptics touchpad by reversing the Scrolling Distance.

xinput list-props $TPAD_ID | grep "Distance" shows negative values for this property I changed.

However, by the time GUI starts up, Scrolling Distance values are positive if I xinput list-props $TPAD_ID

How can I figure out why my changes are being altered or reverted by some program?

The "something" that over-writes my changes is Xserver reloading the synaptics touchpad 39 seconds after boot.