CLI vs CLI

Hi.
tl;dr; 4.2 RouteCollection::cli() - depracated; 5.0 RouteCollection::cli() - removed

In versions of CodeIgniter before 4, the framework did not have the ability to run console scripts bypassing the front controller and it looked like this 
php index.php controller method params

Starting from version 4, it became possible to create a cli() route, as well as run through spark.
In my opinion, the next stage of development will be to abandon the use of the cli() route and switch to only running console scripts through spark.
Now, using the cli route or spark, we load the entire core of the framework. Instead of directly accessing the class that is executed in the console, we load classes: Request - no payload, Response - meaningless for cli, filters, helpers, cache, web part routes.
What if we move the launch of console scripts to a separate core? It will only load the necessary functionality to run the script without all of the above, which is necessary for normal web routes to work.

spark --> console core  <-- base app init --> web core <--- HTTP
                      |                                                                      |
          run console script                                Request, Response, filters, routes, etc
                                                                                            |
                                                                             run web controller