Unfortunately, there’s no quick “just trust the blocks you already have” button. Bitcoin Knots (and Core) have strict cryptographic validation rules, and any mismatch between what’s expected in the database versus what’s actually there means it will start from Genesis to rebuild the chainstate from scratch. That’s just the reality of running fully validating nodes replay is the only way to be certain the UTXO set and witness commitments match consensus.

If you really want to avoid another multi-day resync, the only feasible approach is to grab a fully validated blockchain from a machine you trust that’s running the same software version, same consensus rules, and was started with witness data enabled. Even then, it has to live on the same architecture and OS environment to avoid compatibility headaches. For most people, letting Knots do the clean reindex is the safer bet, even if it’s annoying.

What you’re seeing is actually one of the design strengths of Bitcoin: no shortcuts when it comes to consensus. It’s frustrating in the short term, but in the long term it’s the reason you can be confident your node is seeing the same reality as every other honest node out there.