The reason mocks has its own configuration (and expectations) is because they are designed to be usable on their own, apart from rspec-core.  (For example, you can use them with minitest or cucumber).

rspec-rails, on the other hand, requires rspec-core, and so it's safe to assume the rspec-core config object is available, and makes sense to piggy back on that to present the config interface.