This discussion brings me back to when I was selling computers at Hewlett Packard to the Navy and Air Force. I would ask a support person a question and she would go on a bit longer than I expected, or could explain to the customer.Support people wondered why sales people were so stupid and sales people wondered why we were needed to boil down explanations for the customer
I can relate to this! As a techo, I cut my teeth on arguably the world’s first PC, the Olivetti 101. I slowly worked my way until I had the grand title of Principle Systems Engineer with Australia’s biggest company.
Then I moved to a computer company, where I was the support guy doing all the work in presentations while the sales guy got all the money. So I swapped hats and became the sales guy. Initially I had absolutely no idea what I was doing, but fortunately I was poached by another computer company. Relatively quickly, people realised I was a sales guy that did know what he was talking about. I got the best accounts!
The most help I got was another sales guy who lent me a book on negotiating, which emphasied that you had to know the other guy’s timeframe.
Timing, in sales at least, is everything. Which is a segway to your question about timing in the digital playback world. Personally I think it is a bit of a furphy (Australian slang for an army water wagon round which tall stories were told) but I know I’ll be shouted down.
You can go out of your way to cause timing issues, for example by using I2S - see post above. You can use streaming services where your packet timing is subject to the vagaries of the Internet.
But if your dac is close-coupled to an input buffer, I think there are better things to spend money on than expensive clocks.
Let the battle begin

