You're right, he's comparing the cost for that very simple case. Do anything remotely complex and it quickly becomes just noise.
Profiling is essential when figuring out how to improve your code. What we're doing here is explaining one weird benchmark result.
"Why blocks make Ruby methods 439% slower" implies something that isn't happening here, at least to me.