My reason for creating a clustered index on RID is that

Where using the non clustered index for joins or queries, if the RID was an output of the query or join, then it will be satisfied by an index seek or scan without having to do an RID lookup, hence behaving like an included index.

Else, you will be hit with RID lookup, if table is a heap.

Execution plans also become easier to optimise [seek plus lookup becomes only seek]so SQL can make a better choice of what to do.

Secondly a scan of RID is faster than if it was a scan of nonclustered index, in the cases where scans are unavoidable, 64k reads on clustered index pages vs (8k reads and jumping between non clustered index and Table).