I dont think that's the case. You will see the error message that you have called out in the second case under the following conditions :
* The chromedriver binary cannot be found in all the folders as detailed by the PATH environment variable.
* Webdriver tried querying the JVM argument webdriver.chrome.driver and found an empty value.
This behavior is the same across both RemoteWebDriver and ChromeDriver because RemoteWebDriver internally doesn't do much apart from using reflection to make a call to ChromeDriver only to get the job done.