To implement a Wrapper that actually modifies its child's solution trajectory (e.g. changing the time parameterization), we currently need a dirty hack because of a missing "lift" interface to lookup the proper external InterfaceState.