They have no packages but do a full patch of the system data. Since this is the most complex approach and almost everything can go wrong down to the core they spend most of the time with checking and cleaning state.
Normally its better practice to have the server configuration stored in a declarative way like ansible or similar and only store the userdata in the backup.
So you can fast and easy reinstall your server including all of its config files and then clone the usage data like dbs or files into the new machine. This is more reliable and also faster than just do a full dump of the system.
Sometimes in enterprise environments you’re not allowed to have a proper Linux and you’re forced even as dev to use that thing from ms.
Since hardly any code in the web runs on NT, the wsl is the only way getting your things done. It does what it does OK(ish) but except of that single usecase I would never use it.