I'm glad to see this conversation is still ongoing in a productive way. Now that countdown timers have been officially accepted and incorporated into the framework, it is even more of an impetus on developers to consider the many kinds of people who use BGA when designing interfaces.
Countdown timers enabled by default are an accessibility nightmare. For some people, especially those new to BGA or new to a particular game, 15 seconds (or shorter!) is not long enough to evaluate the game state they are being asked to confirm, realize something is wrong, switch focus to the action bar to identify and click the undo button. For some people, the sudden presence and pressure of this timer induces panic. I've certainly experienced this when trying new games, and needlessly restarted my turn because I didn't expect that pressure while I was trying to understand an unfamiliar game state. Learning a new game on BGA should not be an experience that induces panic.
All that said, I have come around to the position of wanting to support players who find these counters useful and have been making them available as a non-default option in my implementations.