It's hard to pinpoint what exactly is causing this, but here's what is happening. I have (pictured below) a flow of logic doing various checks connected to the block "OnTransformParentChanged".

This behaves (and has been behaving) correctly. And it's this set of nodes that control the kinematics, if I delete it, then the kinematic state never gets changed.

But if I delete the connection entirely, and set it to flatly set the kinematic state to True, it still uses the logic that has been entirely deleted.

Deleting the "Set IsKinematic" and recreating it doesn't update the logic, deleting "OnTransformParentChanged" doesn't update the logic. Yet it's this specific block that is fully controlling the kinematic state of the object, using logic nodes that have been deleted.

This logic functions correctly when used in the VRChat emulator and when connected to "Update" or every other event that I've checked. It is solely the "OnTransformParentChanged" event (and any CustomEvent sent from it) that seems to have this ghost info