> Given this drawback, dependency injection still seems like the better trade-off to me, despite of its higher amount of required boilerplate. Perhaps it is possible to bring some of the explicitness to the dynamic scoping approach, though.

There's a difference between a program that's industrial-strength versus a toy project.

Any program that's industrial strength will require effort in strengthening, irregardless of the pattern chosen.

(Honestly, I really wish dependency injection was a language feature.)