Switching fro cycles to Eevee Workflows?

Hi .

A lot of people will use Eevee as a "setting a scene up in real time then doing a ray tracing rendering as the final result" Then a lot of workflows will be based from backing in and out from thoses differents render engines and the big question is:

"how could we facilitate the backing in and out process more quiclky and efficiently than always changing the engine option in the render menu? " because its quite a pain in the ass to change it in the render menu every time ... am i wrong ? so heres some solutions :

• why do we need two separated engine option ? and not regrouping Eevee and cycles

into a same workflow, and then considering each other as different render viewport ????

• or (less work): change option : we could have a hotkey that change the two engines

the problem is that in this workflow the ctrl-b border render is quite a must have for cycles , so we need to have a ctrl b cycles render inside of eevee to be efficient ..

what do you guys think ?