They want to view the safety offset because they are device vendors doing quality control on their device drivers. I want to include it because I’m a bit of a neat freak sometimes 
getLatencyFromDevice() does include the safety offset but my suggestion to also include the stream latency has not been officially implemented.
Now that you’ve pointed it out, I can see I missed putting it in getLatencyFromDevice() in my fork! However, I’m not too fussed because I’ve never seen a non zero value. Fixed now anyway.