Since most databases support reverse scanning of indexes, it's unlikely you'll see "inverted index" much in the future.
the only real reason for them to still exist is when you're gonna have a query like:
select * from table order by field1 DESC, field2 ASC
Note that the fields are going in opposite directions.
In this case, being able to invert the second field in the index allows the database to use a multicolumn index for this query.
There's work arounds for this in Postgresql (not pretty) but I don't know of any for MySQL.