I personally would prefer the second lesson on recursion (examining the exercises like the OP is asking about) to concentrate on the possible errors, like one-off errors and infinite recursion.
This shows the learners that while there is more than one way to implement something, there are vastly more ways to do it wrong.
Then, later on, when the learner has sufficient practical experience to understand the theoretical underpinnings, they'll both have something to anchor theory on, but also understand that the theory is inherently useful: one does not need to know all the ways things can go wrong, or each of the ways to do it right, if they have tools to prove the solution right/wrong. It's not theory for the sake of knowing the theory, it is a set of meta-tools for development.
I always like to rely on (my) inherent laziness. True laziness is when the overall workload is minimized; not when necessary work is postponed or pushed to others, minimizing just the immediate workload. The latter is just being short-sighted, shitty dev. (Yes, even if your employer demands you do that. They are then deliberately paying you to be a shitty dev. It's a very common and perfectly valid occupation, but produces shit products. Which often sell well, given big enough marketing budgets.)
In this thread, as so often happens in this sub-forum, we've delved deep into the theory and details, without showing the OP or others how it is related to the question at hand.