Replicating data for ease of access
This sounds like the classic case of History versus CurrentState.  Sure, have two tables.  Insert a new row into History and overwrite the row keyed to the user in the other table.

That does lead to "redundant" data, which is a 'no-no' by DB purists.  So here is another approach:

Insert into History, as above.  Get back the AUTO_INCREMENT id.  Then Update the CurrentState with just the id (and user_id).  Then, for accessing the current info, use a JOIN between the tables.