Does the principle of having an "ever increasing index" also apply for NVARCHAR and VARCHAR?
If I understand your question:
It is a good practice to have an ever increased index - that prevents page splits - read about this issue if you are not familiar with it. It is correct also for char values. To make it simple - sql server will fill page after page without having to insert rows in the middle. Think about it as filling phone book - it is much easier to fill it in abc order than randomly insert names.
So the order "abc", then "def" and then "ghi" is ever increasing.
Don't know why do you think that using char columns as indexes is a bad practice - if you need them there you should create them. Yes, creating logic that will enforce ever increasing char insertion is difficult and sometimes impossible, but it still shouldn't prevent you from creating indexes on those columns.
With all that said if you need to enforce ever increasing clustered index you should probably use numbers(identity or sequence)