On the old groovy platform, whenever you changed DTH in the IDE, the configuration was executed, but it also had its drawbacks.
Depending on the driver it was paired with the first time, it may or may not work.
If it was paired with a zigbee thing driver, these drivers do not configure any cluster or attribute, so if you later change to another driver, zigbee switch or contact, for example, cluster 0006, On/Off, or cluster 0500, IASZone, will not be configured.
In the case of a zigbee switch, which is powered by A/C and does not sleep, there would be no visible problem for users, since it would report manual state changes and although it does not report periodically every 5 minutes, the health check function would read the device every 8 minutes (5 min x 1.5) and since they don’t sleep then it would answer and it wouldn’t show up offline in app.
In the case of zigbee contact, it would depend on the type of device and how deeply it sleeps, but the normal thing is that it does not periodically report its status and does not respond to the healthCheck readings and would appear offline after about 2 hours.
If the initial pairing was with a similar driver and a very similar profile, there should be no problem, since this driver will configure the necessary clusters and attributes, for example if you paired with a stock zigbee switch and you change to a zigbee switch Mc or with stock zigbee Contact and you change to zigbee contact Mc.
There are more nuances, for example, my drivers do execute the device configuration with a driver change, but depending on the device it will accept it or not.
For example, tuya sensors with battery sleep deeply and do not accept the configuration when changing drivers, even if you try to configure. Samjin(Aeotec) accept new configuration in a driver change.
Some Tuya multi-switch devices require 7 attributes of cluster 0000 to be read at the first moment of pairing and the device to be in pairing mode.
There are more cases, but with these it is still clear that the procedure is not very clear!!! 
If you are unsure what to do, then there is a process for zigbee devices that configures them without having to uninstall them.
All this explanation is for zigbee devices, for zwave it is different.