It seems that, on avatars with FT enabled, remote clients run the animator for a frame, and then improperly re-record all of the animator default values (perhaps because the animator is being toggled or reset improperly or otherwise). This issue ONLY happens on remote clients, not on local. The bug seems to require Face Tracking to be configured with a target mesh and a few valid blendshapes AND for Eye Look to be enabled (even if it's not configured in a FT eye look mode).
This breaks many avatar systems, since the basis state of the avatar contains all of the "unanimated" defaults, and many controllers (especially those with WD on) only have clips which target the opposite of that state.
This is likely the root cause of the recent partially-weighted AAP and sync parameter issues reported regarding FT (although I don't believe it's actually a sync issue).