Yes, 16K will have an impact, especially in 16bit or float. Many years ago, a real problem to load, especially when an HDRI had to work as background as well, then perhaps more than 32-64K to get sufficient data in the camera view. Which sometimes leads to manually resampling the image for what is needed.
I will run some tests with the current release and then file a report. Fingers crossed, it will help.
Specify exactly what you like to do and why you think that is unclear in the EULA. Be super specific with your project.
From my point of view, general questions are challenging to answer as they require thinking through all possible options.
After all, the EULA is written to be as general as possible, while it is pretty simple, from my point of view, compared to other papers I have seen.
I don't think so; the path would not be the same. I re-read the initial post, just in case I missed something.
Projects transferred need to be saved with Assets.
You did not mention that you like having it on multiple machines as copied data.
Data that is just copied will lead, at one point, to a disaster. Just wait for it. One sequence was color space converted on one machine, not labeled.
Now during a deadline, this was forgotten. The deadline might be missed: The client lost.
Central data storage is needed, and I can't support that here, as it is way out of the scope of this forum, but I know someone will tell me to use Dropbox.
Two things why I don't participate in such things.
Constant access open in the internet to your production machine is kind of a risk. Production machines in high-end facilities are more often than not disconnected from any web-based sources. Guess why.
At one point, they are easier to hack, and you get shut down with any internet hick-up.
This question is more for hard-core IT people who know all the details about connecting different machines and can establish security protocols.
Here is my suggestion. I would create a Null Object and apply User Data to it, Float, Float, Real, and 0.001 for the settings. See image.
Go to the Timeline, select the Time Scale keyframes, and Shift/CMD, drag these keyframes to the User Data. (CMD or Control, based on your settings)
This Null object, with a good name, can be dragged into the Asset Browser.
When you need it for another scene, drag this Null object into the Object Manager, and Shift/CMD drag it to the time scale.
I'm not aware of a faster workflow, assuming you like to add the keyframes while having worked already on the new project.
Otherwise, please make a copy of that project with the Time Scale animation, empty it completely, except for the Time Scale, and store that c4d file in the Asset Browser. This will open a copy of that, but to be clear, it will not inherit its Time Scale Animation to an existing scene.