That is a common scenario.
Like you mention, it is very dependent on workflow and culture; often users aren’t encouraged to go down paths less traveled, regardless of the potential.
Ideally they will give you enough leeway to get the job done, but this typically puts the onus on the computational designer who then has ends up working far too many hrs. This is justifiable if what they are learning and the mistakes and successes can be applied to the next project, as well as the obvious increased skillset.
Rhino.Inside.Revit seems to be most applicable to specific workflows that would otherwise be mundane and lengthy for the user to do through the Revit UI.
The smaller and more generalized the workflow the easier it is to get others involved. That said, most scripts require some knowledge of parameters, types, categories and filtering, which the average user might not be aware of and can easily cause havoc in a project.
Yup, it really does depend on the culture and the people involved.