Issues reconfiguring backups after Windows -> Linux OS migration

Welcome to the forum @noodle

This path should be super simple, right? The question is whether it’s what you want to have.
You can do cross-platform restore from your old backup if you have space to keep it around.

If you mean CLI docs for purge, I think you found a bug from 2016 on a secondary reference.
Primary references are usually better, but sometimes built-in help is more current than manual.

--no-auto-compact = false If a large number of small files are detected during a backup, or wasted space is found after deleting backups, the remote data will be compacted. Use this option to disable such automatic compacting and only compact when running the compact command.

looks about right to me, or at least not backwards. The reason the suggestion is suggesting a

delete all filesets and make sure the --no-auto-compact option is set

is if you don’t, data in the destination gets deleted because it suddenly became wasted space.
What this plan is trying to do is to let you reuse your existing destination data in a new backup. Situations where the goal is to avoid big uploads might appreciate that. Others might not care.

You still wind up with current version. Converting history is harder (thus the awful procedures)
because things like file permissions are different between OS, so are best obtained at backup.

Change of Duplicati server (+ OS) without losing the remote data was a 2023 dev explanation, question the wording. The raw data blocks are at destination for awhile, but old backups aren’t.

proves that some level of conversion is possible, but further comment would need developer. Possibly it boils down to a question of priority. Things that are rarely asked might be deferred.