As long as you're using WASAPI exclusive or ASIO it shouldn't matter. Kernel streaming is a leftover from the XP-era that's depreciated, so best to avoid it if possible.
https://wiki.jriver.com/index.php/ASIO
https://wiki.jriver.com/index.php/WASAPI
Shouldn't matter. WASAPI is more 'modern' and tolerant. ASIO depending on the implementation can be 'slightly' more challenging. The DacMagic ASIO driver worked well back in the day IIRC.
JRiver's way of 'talking to' ASIO drivers is really good, and I actually have been surprised at how it's handled professional interfaces that other, playback only software has struggled with.
The reason ASIO was created, the primary reason it still exists is latency.
So back in the day, it was almost impossible to 'tune' windows for really good, near real time latency during recording and production. If you're doing playback, if the WASAPI driver provided for your target device is good, there's not much reason to go with ASIO.
Latency re: playback isn't a huge concern. A) you can be off by like a few ms and there won't be a difference (look at frame times for the kind of content you consume) B) unless you're doing something weird, the target D/A is using it's own clock anyways.