It sure seems like an expensive solution for a $2 problem but that would be my view.
I am well aware of potential for test execution methods potentially changing the results I do software performance testing. If the test is set up wrong it is possible to show either very good or very bad results even when the software should perform perfectly.
Based on 'common' uses for a car PC (music, GPS, and video playback or capture) the read/write cycles will be fairly low and a system like you describe not likely to change the already low failure rate. In fact the elevated read/write cycles in your tests may contribute to some of your failures even without motion.
Very cool though.