While this may have been the intended behavior, the javadoc states "This method blocks until the channel is readable, and then the message is read." which disagrees with the implementation.
By contrast both writeBlocking and sendBlocking overloads with timeouts measure time since the request began, so it seems reasonable to standardize on that behavior.