Is nbdcopy actually touching the data consumer side or is splicing to /dev/null ?

It's actually copying the data. Splicing wouldn't be possible, since NBD is a client/server protocol.

The difference between nbdcopy ... /dev/null and nbdcopy ... null: is that in the second case we avoid writing the data anywhere and just throw it away inside nbdcopy.