MPU-6000 Software Support

For evaluation purposes, we've been using the MPU-6050 Sensor Board for the Atmel AVR UC3, attached to an Atmel UC3-A3 Xplained board, as recommended in the documentation. I've been using the MotionApps software stack EMBEDDED_MOTIONAPPS-MPU6050B1-Rel-Atmel_UC3-V2_0_1_6x-2011-12-09-1831.zip

We'd now like to migrate this to our final design, using a CPU that supports SPI but not I2C. Presumably that means using an MPU-6000 or MPU-6100. I have a few questions:

1. What's the difference between the MPU-6000 and the MPU-6100. Are both easy to use on SPI, assuming I don't need them to talk to an external magnetometer?

2. Are these chips intended to be supported for the forseeable future? It seems to me that the 6050 series and the 9150 series receive the most attention from the manufacturer.

3. And most importantly, I need to know how to configure the MotionApps software for the SPI-based chips. I can write an MLSL, MLOS, and UStore interface; and in fact have done so for a bit-banging version of I2C to the MPU-6050 on my CPU. What I need to know is how to configure the #defines for the software stack if I'm using an MPU-6000. I see defines for CONFIG_MPU_SENSORS_6050A2, .._6050B2, .._MPU3050, etc. But I see none for the 6000 series. What's the appropriate configuration #define? Similarly, there are different versions of some .c files, e.g. mldl_cfg_init_umpl_6050a2.c, dmpDefaultMantis, etc. I confess I don't understand the chip revision references, such as A2, B1, Mantis, etc. In a nut shell, what software stack would I use, and how would I configure the defines?

Thank you.