The entire point of a driver is to provide a common API on the front-end(i.e. file system access), while accessing wildly differing hardware on the backend, such that the software(Windows) cannot tell the difference. When Windows requests the device information from the driver, that information is where Windows gets told the specifics which get mirrored to the user if its requested.
Any 'differentiation' would simply be a request of a boolean variable in the driver.
Either way, this has nothing to do with UI.
Could what you suggest be done with split UI? Absolutely.
Will it. No. Maintaining two distinctly different interfaces is pointless, prone to bugs from split development, makes it harder to teach people the interface(depending on which), and in the end doesn't really provide a lot of value over just having one. You really do need to pick your poison and stick to it. Tech evolves. It happens.