Cycles is not Cinema :)
So, standard shader creation takes long? What modelling slowdown do you experience exactly...?
I don't have any issues at all on OSX Mojave with R19...
I already covered nodes quite deeply in my training :)
They can be used completely separately. I rarely use set context except override and that is mostly for UV manipulation...
Get context simply provides you with scene/object and other data. I don't understand all the stuff in there thoroughly but have a solid insight. In reality you don't have to understand it all to make cool shaders :)
Here is a quick stab at circle shader. I have no clue how excatly circle preset is done, but I suspect it uses pretty much the same concept as I did. This can give you insight how this is relatively simple to do.
Circle.c4d
Bevel tool is completely unrelated since it deals with geometry. It is 100% MAXON development. You are right about patents, some are simply, err... silly...
Here is a simple "rose curve" approximation. This can be used to see how shapes/patterns are made.
Try to tile it and transform UV's, a lot of interesting patterns can be made :)
Rose_Curve.c4d
Preferably yes, although it is not a written rule. Just keep in mind that Cinema rotations start from Z axis and use freeze transforms to your advantage :)
The functionality is intact and existing COFFEE stuff works, however you can't create anything COFFEE related anymore. I suggest you redo the scripts or whatever you have with Python...
I would say so, but I am afraid this exceeds my capabilities, at least SSS shader does, although fake SSS is possible with AO. As far as Bevel shader and ocean shader that would be doable, will try :)