Odd, I don't have this issue while using LDAC but then again I am using either the NW-ZX2 or NW-ZX300 as the audio source. Perhaps the stack that's used by Google in Oreo has issues, after all Oreo is not currently a finalized product. Either that or the device you are using (Google Pixel or whatever) does not have a fully LDAC compatible bluetooth controller and isn't able to perform at the required power output levels (LDAC requires more power to operate than APTX on the source side), in fact it is quite the power hog as far as the NW-ZX2 (which runs on Android 4.2.2) is concerned, the NW-ZX300 lasts a lot longer in LDAC operations but there isn't a whole Android OS with a whole bunch of non required services (for a DAP that is) running on the thing.
Either way, bluetooth controllers power requirements when it comes to LDAC are extremely regulated, only a handful of controllers match the specs, it's not just a matter of loading the LDAC stack and calling it a day, if you do that you might certainly run into issues.
The power requirements issue is the very reason why Qualcomm did not push the boundaries of AptX HD all the way to LDAC's 990kbps bandwidth, another reason however is latency, something in which AptX HD performs better than LDAC does.
LDAC was purely designed to carry high definition music tracks over bluetooth with as little compromise as possible when it comes to quality, that's great for audio/music listening, not so much when it comes to watching movies or playing games.