I can understand why you might be skeptical. However, I have learned over the years as a developer investigating update issues that the constraints placed upon the update process to ensure compatibility and resiliency are complex.
The nature of the process used for most Feature Updates requires user data and preference migration and transfer. Notably, an entirely new installation of Windows is created and then existing user data and preferences are migrated or transferred as appropriate. There a variety of good reasons for this from a technical standpoint, but it has certain complexity and performance trade offs so is only used for certain types of updates.
Other types of updates use an in-place upgrade methodology that doesn’t require user data and preference migration but has certain characteristics that make it currently less suitable for major feature updates.
The nature of the process used for most Feature Updates requires user data and preference migration and transfer. Notably, an entirely new installation of Windows is created and then existing user data and preferences are migrated or transferred as appropriate. There a variety of good reasons for this from a technical standpoint, but it has certain complexity and performance trade offs so is only used for certain types of updates.
Other types of updates use an in-place upgrade methodology that doesn’t require user data and preference migration but has certain characteristics that make it currently less suitable for major feature updates.
Thanks!