One MySQL table for all data vs Several Different Engines MySQL Tables
Simply, use InnoDB for everything.  MyISAM is going away in the next release.  In almost all cases, InnoDB out-performs MyISAM.  About the only advantage with MyISAM is disk space.

With millions of rows, you will appreciate InnoDB's automatic recovery after any crash.

It is rarely wise to make two tables be 1:1.  Your suggestion for that is based on one table being constant; the other being frequently modified.  But I would suggest that "frequent" is 'many times a second', not 'a few times a day'.

Don't design the schema without sketching out the SELECTs.  You have POINT and SPATIAL, but what will you do with such?

Glancing at the tables...

Use SHOW CREATE TABLE; it is more descriptive than DESCRIBE.

Don't use BIGINT (8 bytes) unless INT (4 bytes) won't suffice.  You would need to hire nearly all the adults in the world to exceed what INT UNSIGNED can handle.

JOIN can be pro or con.  But it is rarely a deciding factor.

Use utf8mb4 from the start.  (DESCRIBE omits that bit if info.)

Use AUTO_INCREMENT only if there is not a 'reasonable' column (or combination of columns) that make up a 'natural' PRIMARY KEY.

TINYINT UNSIGNED is limited to 255, not enough for odometer.  MEDIUMINT UNSIGNED goes up to 16M.

Do not PARTITION without a good reason for it.