Clearly this has implications for other software that we were unaware of and in fact, you are the first person to flag this as an issue.
I can only suggest that you revert back to v3.07 of the API, or contact the author of Fastlane to see if they can help you on using the alternative S/N that is created by later versions of the API. In the meantime, I will ask the S/W team the review this feature to determine how useful it actually is and whether we may be better to revert to the old approach in the next version of the API.
What would suck is if you email dsdplus and they change something to deal with this issue, and then RSP team reverts back to the old approach.