Return of key functionality for Windows Autopilot sign-in and deployment experience

All of the MB replacement scenarios mention reimaging of the device which might not be acceptable for many users who got their MB replaced and they have a lot of customizations on their device. What is the recommended way of handling such scenario - user has Autopilot device, Dell device got its MB replaced, and now we're facing TPM errors on the device, Teams is not working etc. which are preventing the user from working but we want to keep the device state without reinstalling?

Device in the Autopilot list is reporting as "Attention Required" which says "A hardware change was detected on this device. It won't automatically receive an Autopilot profile when it's reset unless you register the device again".

I used the command "dsregcmd /forcerecovery" which seemed to reissued the AAD and Intune certificates which fixed the TPM errors, registered the device in Autopilot again using Get-WindowsAutoPilotInfo, however, there are two Autopilot objects for the same device now, there are still some issues and I'm not sure how to proceed in such cases in general.

Is there any recommendation which process to use without reimaging the device?