While debugging #8 there really was no other option than to clone the affected classes into the application project and re-instrument them with trace, as there was no other way to determine the paths chosen from the log output, even when configured to output at the finest level.
Eg take this section of code https://github.com/ibm-developer/ibm-cloud-spring-bind/blob/master/src/main/java/com/ibm/cloud/spring/env/CloudServicesConfigMap.java#L106-L126 There's no way to know which of the reasons null is being returned.