Is MySQL smart enough to not do a full table scan for LIKE or NOT LIKE when there are other conditions?
Given NOT LIKE '%...' cannot use an index and id can, provided a index (include primary key) begins with id, then it will be used.

EXPLAIN [EXTENDED] {query} will show what indexes the query planner plans to use for the query.