Eh, I think your question has essentially defined away any possible affirmative response. You're essentially asking if a language with the keywords async and await, but with no notion of concurrency, does anything concurrently. I mean, the answer is no, just the same as a language with a for construct that isn't actually backed by a looping mechanism doesn't actually have loops.
If you're asking about the "why" of async / await, I think the original proposal has some insight here, as well as the reasoning of the other languages that implement it. But fundamentally, I think async / await assumes (at least what looks like) the ability to suspend execution and continue it later.