Unless you are setting the configuration to affect how glTF assets are loaded with the Babylon loader… in which case, the only way to do that now is via DracoDecoder.DefaultConfiguration like Seb said.
I didn’t think of this possible use case when replacing the DracoCompression with DracoDecoder in the glTF loader. Is it worth putting it back to DracoCompression? @bghgary