[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] porst17:
Short answer/TLDR: No, setting the developer options often results in worse bluetooth audio quality because it limits the choices during bluetooth audio codec negotiation. The options are there for debugging.

Long answer:

The codec selection in the developer options only sets the codec preference. Bluetooth audio selection is a negotiation process between two devices. The SBC codec is defined as the bare minimum codec in the bluetooth standard. It will always be advertised by a bluetooth audio device (to conform with the protocol). The other codecs are optional and if you select a specific one in the developer options, this codec will be advertised in addition to SBC. So if your headphones support the LDAC, ACC and SBC codec and you select AptX in the developer options in your phone, the negotiation result will be the lowest common denominator SBC - which is the worst of all. So your best choice in the developer option is to set it to "System selection". This will always result in the best codec supported by the two paired devices.

Now regarding AptX in particular: With Oreo, Google made it easy for manufacturers to add additional bluetooth audio codecs. SBC, AAC and LDAC are part of AOSP. SBC is supported by all devices, AAC is mostly used in devices that have been designed for iPhones and LDAC is Sonys very high quality proprietary codec for which they donated the encoder code to AOSP. Unfortunately, LDAC is only supported by very few audio devices (headphones, speakers, hifi systems ...) and those are usually on the expensive side. AptX is kind of widespread and available in many mid-range audio devices. AptX-HD is still quite new, but the number of supported devices is growing. However, AptX and AptX-HD are Qualcomms proprietary codecs. Your device has to support it in hardware AFAIK and the software side of the codec is NOT part of AOSP. The codec library files I mentioned above (or similar ones) should be present in the Stock ROM. They act like a plugin. Put them in /system/lib(64) and AptX/AptX-HD will be advertised during the negotiation. If the "plugin" is not there, a lower quality codec will be used - most often the SBC fallback - even if you select AptX/AptX-HD in the developer options.

Bluetooth calls are one thing. AptX and especially AptX HD can certainly help with audio latency (up to a factor of ~6 less latency on the codec side compared to SBC) although the difference is usually barely noticeable during calls (because there is no such thing as "lip sync"). But if you experience connection problems, frame drops or crackling audio, this is relatively independent of the codec used (because bluetooth codecs usually adapt their quality based on the quality/bandwidth of the connection). So, yeah, maybe some bluetooth devices maybe just don't like each other.

The main concern with bluetooth codecs is media streaming to headphones, speakers and for some people (car) hifi units. That's where you may notice a significant difference in quality.

Regarding developers: If users have issues and help debugging or even provide a fix, developers are usually more than happy. Because that's what I call a community and it is a lot of fun to work with such a community. However, if people are just complaining and let all the work to the developer, I fully understand why devs become demotivated and leave.