You are ignoring that even single threaded code has a lot of sources of concurrency and side-effects; memory/caches, branch prediction, prefetching...
Watch the talk and look at the examples. Most of them are single-threaded; a bad hash-function causing bucket collisions and linear inserts; SQLite using an indirection table, killing speculative execution and code prefetching.
Those two wouldn't really show up in a sampling profiler, because they still take up a tiny amount of time.
Sampling profilers show you where time is spend, Causal profilers show you what performance side effects every line of code has.
I have literally discovered and fixed the "bad hash function" case at work using gperftools. I'll watch the talk again anyway.
If you are never doing concurrent work then there will never be any code where a speed up doesn't affect total runtime because it is waiting for some other work. As I understand it that's the gotcha that Coz fixes, but it doesn't apply in single threaded code.
But I have never got it to work so maybe I'm missing something.
Maybe it's just easier t interpret. Sampling profilers can be a bit confusing, and debug info doesn't always work as neatly as you'd like.