Integrations are pieces of code that is “inserted” into the core, so the core needs to be restarted to get this updated pieces.
HACS provide integrations.
Addons, which is available with HAOS and supervised installations, are independent servers (Docker cobtainers) and most of them also require an integration for HA to access it.
Addons can often be run as independent server on other devices too or as Docker containers on installations that do not provide addons.
Addons is essentially just Docker containers managed by HAs supervisor code.
Sorry, but this is really a problem with whoever is developing that HACS integration. The developers need to do a better job with Quality Assurance on the code and make sure it is correct BEFORE publishing it for you to apply.
Unfortunately, when you perform these updates, you are at a risk as far as stability and the update you applied not working as the updated version until you perform that update.
Unless you have a specific need to update that HACS integration because something is broken, I probably would hold off on updates until end of day (or whenever you typically stop seeing updates which would be the end of the developer’s day) .
Look, I get it. I work as a Network Architect/Engineer. I never apply code to network equipment unless that code is “General Release” (not beta or alpha code) unless I have a specific thing that is broken that non-General Release code fixes. And I do not typically deploy that general code until it has been out for at least 30-days, preferably 60-days so those who adopted it first have found all the bugs that were not found in alpha and beta testing…I guess you call them the gamma testers if I follow the Greek alphabet correctly.