Yes it seems alright. And yes, there will be things happening along the signal chain if you're using this. As you have noted, there is resampling being the scenes, and I'm certain there's a lot of other signal modification between your original file and what is output by the bluetooth receiver. It's a well known issue with computer audio in general. If you're using the normal audio subsystem of your computer OS, it's already not guaranteed to be bit-exact (it's usually not), so for professional audio, people tend to use specific access/drivers (such as ASIO). Then you're adding bluetooth in the equation, and the signal is further modified.
-0.95dB is not much in terms of audio and probably nothing to be concerned about. The resampling would be a more important concern here, as I'm pretty sure it's not state-of-the-art resampling, so it's probably adding some distortion.
As to the DAC's outputs loading, you get -1.87dB attenuation with a 1k load, which is again not that much in terms of audio. The datasheet states the output can be loaded with 1k, and they can. It's just attenuating the signal a bit, less than -3dB. That said, there is no reason to load them with such a low impedance - I see absolutely no benefit unless the following stage has 1K input impedance and you don't want to be bothered with buffering the DAC outputs.
All in all, if you are expecting a "bit-exact" signal output with an exact full-scale output, using a computer's audio subsystem and bluetooth audio is definitely not the way to go IMO. For audio listening, it's alright. If you're using that as a signal generator... I would recommend using another approach.