The 3rd preview of Android "Marshmallow" does no longer contain any hint of the SIM Access Profile, so it seems it was accidently included in the first preview. At least it shows that Google added basic support for rSAP, so maybe more phones will add it in the future.
There is still no solution for the 64 bit incompatibility, but I'm working on the MediaTek version.
The new MediaTek phones with the MTK6732 and MTK6752 chipsets cause problems with my rSAP app when they run Android Lollipop. Android/Linux seems to be running in full 64 bit mode, although the ROMs still contain the unused (?) 32 bit files. My installer app sees the 32 bit files, happily replaces them, and ... nothing happens. The app shows the infamous "is this a compatible phone" error.
The same seems to happen on recent Qualcomm phones, like the Nubia Z9 mini.
The Qualcomm fix should be easy, the MediaTek fix will be a bit harder, because I had to use some "voodoo" to make it work. I'll let you know when I have news.
Today I installed the Android M preview on my Nexus 5 to check if there are any problems with my apps, and experienced a strange surprise: Android M supports rSAP. Well at least it supports the Bluetooth profile, but I could not really make it work. Maybe I messed up something on my phone, maybe it's simply not finished. But it seems Google at least recognized that rSAP might be a nice feature!
So my phonebook app still works with the Android M preview, my rSAP app doesn't, because the built-in rSAP blocks it. Let's see what will happen in future updates.