The purpose of jumpstate is to bring a pre-existing previously untracked resource under Wildebeest management.
jumpstate could be misused though to force Wildebeest to consider a resource to be in a different state in the case where you cannot migrate it cleanly because of failing assertions. Using jumpstate as a workaround like this could compromise the integrity of the resource you're managing.
A solution to this is TBD. Some options are:
Don't allow jumpstate to be used on resources that have a state - i.e. ONLY allow jumpstate to be used for bringing untracked resources under Wildebeest management
Put a big warning banner on it
Require some "are you sure?" confirmation. For the CLI this could be a --force switch