No, it's ignored by the CFML runtime except in a CFC context. I usually put it in to indicate that it's an internal implementation detail versus something deemed to have a stable API. In this case, you can't call the functions without modifying script.cfm itself, but outside a custom tag context, that's not always the case.

I thought access attribute only means something when the cffunction is defined inside cfcomponent?