Could this facilitate an update to the A2DP profile to enable higher-fidelity wireless audio transfer, as an alternative to aptX?
A2DP is a BT profile or service. It is designed to uni-directionally transfer an audio stream in up to 2 channel stereo, either to or from the Bluetooth host. It is independent of the speed of the transfer. It includes mandatory support for the low-complexity SBC codec. The Sub Band Coding, SBC, was created many years ago by Philips as a coder/decoder for converting analog audio to digital format to be transmitted by BT from a source (transmitter) to a sink (receiver). Not all codecs are equal. Some are highly complex and capture more audio for coding, e. g., MP3 and AAC, than others. This generally requires a very fast microprocessor to slice the audio wave into many parts and assign it a code for each part. The more slices, the higher resolution or bitness of the audio. SBC coding is the least common denominator of the audio coding done in BT. In other words, all manufacturers of BT devices (both source and sink) must adhere to the SBC spec. This makes the BT A2DP profile compatible across all BT devices. Anything less would be chaos.
The Apt-X codec is an alternative to the SBC codec. It is a higher resolution codec for streaming audio uni-directionally. It, of course, requires the Apt-X codec at the source and sink. Absent this, the BT A2DP profile defaults to the lower resolution SBC codec to stream the audio to be compliant with the BT spec. So, if you prefer low resolution audio with lots of latency for maximum compatibility, you should stick to the SBC codec when you design a sink or source BT device. It is also the most cost effective solution as the microprocessor mentioned above is slow and cheap. If however, you desire high resolution audio for high fidelity and low latency of transmission for acceptable lip synch between the video on your mobile device (phone or tablet) and your wireless BT stereo headphones, then you have an alternative with the Apt-X codec which provides better audio resolution and low latency. If your sink or source has a fast enough microprocessor, you can load the CSR Harmony BT stack (program) on to it to take advantage of Apt-X coding. This BT stack is proprietary to Cambridge Silicon Radio, CSR, and requires royalties to that company to use it. The audio resolution and latency of the Apt-X is very close to what you get with a wire. So it approaches the sound quality of the original audio content.
There are alternative audio codecs to Apt-X, but they aren't consumer products and are very costly. As an example, the wireless microphones on the lapels of broadcasters in Hollywood have an extremely low latency, 2ms, compared to 28ms - 35ms for Apt-X. The Hollywood wireless microphones used by rock stars in concerts use a propriety wireless transport. They typically cost $2000 per mic. The wireless audio receivers in their ear aren't consumer products either, and are also very expensive.
The IEEE sig for Bluetooth only controls the SBC code to assure compatibility. If you are a radio company and want to enhance how the audio is transmitted over BT, then you need to create a BT stack and hope ALL BT manufacturers support it. CSR, now a Qualcomm Company, has done a great job of promoting their BT stack over the years. Eventually, all roads will lead to the Apt-X codec for the reasons given above.