InnoDB Table has backed up INSERT and UPDATE queries, high CPU
Many things can be done to speed things up...


Use FLOAT or DECIMAL, not VARCHAR for latitude and longitude.  (This is one of many things to shrink the record size.)
Do not INDEX boolean values like clocked_in and public_post.  (The optimizer is unlikely to ever use the index.  And it is costly to update.)
Don't split DATE and TIME; use DATETIME instead of VARCHAR.  (Shrink and ease of use.)
Don't have a table with lots of fields, then spend most of your time INSERTing only two columns.  (Perhaps you meant UPDATE?)  Perhaps have a separate table with the log of clock-in/out?
How many different values are there of order_type?  (Consider using an ENUM or "Normalizing" that field.)


Was that the entire PROCESSLIST?  Or was something other than 2-column INSERTs operating on that table?

How much RAM do you have?  What is the value of innodb_buffer_pool_size?