First, the design basis of the composite tracker is “newer data is better.” So, when one of the inputs provides newer data than the composite has seen so far, it will use the newer data. It bases this on the “last_seen” attribute, or the entity’s “last_updated” field if it doesn’t have a “last_seen” attribute.
Binary sensors (or “router” type trackers), however, are typically much better at indicating when a device has come home than they are determining when a device has left home. So, by default, only the “to home” transitions are used for these types of inputs. So, e.g., when a GSP tracker shows the device has left home, a lagging binary sensor or router type tracker won’t prevent the composite from also changing to not home. Setting “all_states” to “true” can override this default and cause all state transitions of these inputs to be used. That is only recommended for inputs that don’t have a serious lag changing from home to not home.
Looking at your composite configuration, I don’t see you using the GPS device tracker. So, I’m confused about how you’re trying to use it.