And then what?
As David describes, at best it gives you some potential Things in your Inbox. They after not even useable or part of your system until you go in and accept them.
OK, let’s say that someone makes the changes to the core of OH to automatically accept Things in your Inbox. You still can’t do anything with them because their Channels are not linked to any Items yet.
OK, let’s say you have Simple Mode enabled and Items automatically get created for all of your Channels. Now what?
All you have are a bunch of Switch Items. They are not a member of any Groups. Your Rules don’t know anything about them. That won’t appear on your sitemap or HABPanal. For all intents and purposes all you have are some disembodied Switch Items without meaning or function in your home automation.
On the other hand, if you do have a network binding linked Item that is meaningful to your home automation (e.g. I issue an alert to my phone’s when someone attempts to trigger it through OH but the service that does the deed of simulating pressing the button is offline) you will want this device and the Items and Things to be statically defined so you can write Rules and display then on your UIs.
If you wanted to get fancy you could probably create some script that interacts with the OH REST API to accomplish much of this. But it’s always going to require a person to give that Switch a meaning.