I'd still prefer a body with a good commit description, since review descriptions are not attached to the history.
I've been thinking about this a little recently, the conversations that determine the direction of a product are not part of the history, if a repository is shared there's no way to see that information without going through emails, or going through issues on GitHub or Bitbucket or whatever else.
Is this something we can change though?
As you mentioned, these conversations happen everywhere including offline meetings and hallway chats.
On GitHub, single-commit PRs automatically have their body text set to the body text of the commit. (Annoyingly, GitHub doesn't reflow the body text, so it looks "jagged"...)
For multiple-commit PRs, I usually just give some surrounding context and let the reviewers read each commit message separately (with the three dot button).
Most teams automatically put a link to the corresponding code review in the commit message/body.