You're conflating two different issues. The file "bindresvport.blacklist" is for the "bindresvport" function only, which allows binding a port < 1024. This function is not implemented in the kernel, it's entirely in glibc. Furthermore, programs using it are rather rare: it's basically only ever used by a few portmap-based programs, like NFS or yp.
This new kernel functionality is for the much more common case of basically every program that makes outgoing connections (or does a bind with port specified as 0).
So the kernel functionality does not obsolete bindresvport, and bindresvport does not allow doing what the kernel functionality does.
The bindresvport workaround is necessary, because there isn't really any unallocated space < 1024.
The kernel workaround should really not be necessary, since nobody should actually be allocating fixed ports > 32k. Those are reserved for ephemeral allocation, and there's plenty of <32k ports that people could be using instead. But, a glance in /etc/services shows quite a few *official* services with such ports assigned, never mind all the random ports private services might be incorrectly using. So...despite it being terrible that it's necessary, this feature does sound useful.