Thanks for your input, Rajashree Bhattacharya, but your answer was not the correct one. While that document you shared does indeed describe methods for restricting Adobe applications from accessing Adobe services via the network, it doesn't address my need, which is to restrict the Adobe applications and local services from running at all when certain user accounts are in use on the system.
The route I have chosen to address my problem is to install Creative Cloud in a version of macOS running within a virtual machine on the system, so that all Adobe software and local services required to run Creative Cloud can be constrained to the host running in the VM (and fully restricted when the VM is not running). Unfortunately, this means I am unable to use the entirety of my system resources when using Creative Cloud, as the VM doesn't carry through the same resource profile as the native host. But I can then log into a user account on the system without unwanted Adobe software and services running and using system resources when they are not needed.
My product feedback would be to allow for Creative Cloud installation for the current user only, without installing services that are always run for all users.