There's a lot more to programming than creating and calling functions, but I'm yet to see an interviewee struggle with how functions work in their putative "best" language but they're otherwise brilliant. You can't be progressing very far if you're burning that much mental effort on the very, very basics of the task at hand.
By starting with abstraction and moving towards the concrete, you're completely fighting everything about how we experience life and learn. Nothing else works that way. The only abstractions you can teach that way are series of words that students can mouth without understanding, but have no true comprehension of.... gee, that sounds a bit familiar.
As for the rest, I disagree that I'm fighting that standard learning pattern. In nearly every subject, we start with a generality and then move into specifics. We learn about the Roman Empire before we learn about Cicero. We learn about teeth before we learn about incisors. We learn about protons before we learn about quarks. We learn about function calls before we learn the standard library. We learn about China before we learn about Beijing. Almost all learning is performed through iteratively refining a central abstraction with increasing detail.
No one would argue that you should know the turn by turn direction to drive from the White House to the Liberty Bell and use that to generalize how to read a map. We don't force kids to memorize Harry Potter and then later expect them to generalize that our into literacy. History courses don't start with Supreme Court cases and wait until students generalize out the Constitution.
By starting with the abstraction and moving toward the concrete, we give the information context and allow the students a good mental framework to build upon as they learn the details. Starting with the concrete and moving towards the abstract is needlessly confusing and robs the students of the firm intellectual foundation that they need to understand the subject.