It is helpful to the admin that looks at the kill message and records this information. OOMs can come in bunches.
Knowing how much resource the oom selected process was using at the time of the OOM event is very useful, these fields document key process and system memory/swap values and can be quite helpful.
Also can't you disable printing the oom eligible task list? For systems with very large numbers of oom eligible processes that would seem to be very desirable.
We have some servers that have many thousands of processes and printing them all, especially as there may be several oom events that occur can occur in quick succession, this can be problematic and can result in print rate limiting.
Having this information with this message is of extra value in that case.
We've included it on the many thousands of linux systems that we've shipped and also on our internal linux systems and for us it has been helpful.
Also, on our systems we set the Killed process message to pr_err as opposed pr_info as we want just that message being sent to the console.
Customers and our internal support people find this message in that format valuable as they want to know when OOM events occur and so this message gives them a decent amount to go on.
Very few messages go to the console, to avoid clutter, but this one that people agree belongs there.
I'm not sure that change would be supported upstream but again in our experience we've found it helpful, since you asked.
Thanks.