In the documentation it states
'A task that is not on the dependency network cannot have an early schedule or late schedule; hence, it cannot be on the critical path.'
However, when autoscheduling a task that has no dependency is on the critical path.
All supported releases
A task that is not on the dependency network cannot have an early schedule or late schedule; hence, it cannot be on the critical path is a true statement but the same task can qualify to be on the critical path in other ways (0 float, longest duration, etc.).
The calculation goes through the rules and if the task qualifies to be on the critical path on just one rule then it will be.