Luis situation is likely different from Kelly's. Luis situation would only affect a Concurrent User licensing type. Perhaps following might explain it.
Key points:
Drone2Map is currently designed to use Advanced license.
Drone2Map and Pro reads the license setting from the HKEY_CURRENT_USER registry hive.
Luis mentioned he changed the setting in
HKEY_LOCAL_MACHINE\SOFTWARE\ESRI\ArcGISPro\Licensing\ARC_PRO_AUTH_TYPE
Changes made here should not affect Pro or Drone2Map unless its in this unique situation.
If you do a silent install of ArcGIS Pro and defined the 3 parameters, ESRI_LICENSE_HOST, SOFTWARE_CLASS and AUTHORIZATION TYPE, it creates a license setting in the H_KEY_LOCAL_MACHINE registry hive. It also creates a LOCK_AUTH_SETTING which is set to true. What does this mean? When you start ArcGIS Pro, it will look to the license setting in H_KEY_LOCAL_MACHINE and copy it to the H_KEY_CURRENT_USER registry hive and open Pro using that setting. Because Drone2Map licensing mechanism is ported from Pro, it will likely share the same feature. It is possible Luis has this configured on his machine. If he changed the ARCPRO_AUTH_TYPE in H_KEY_LOCAL_MACHINE to STANDARD, it is likely copied to the H_KEY_CURRENT_USER registry hive. Pro will attempt to use a Standard license and fail. It can only use the Advanced license.
In any other installation option, Pro will look to the license setting in H_KEY_CURRENT_USER. If there is a previous setting, it will use that setting. If there is no none, it will create a default setting.