That's an interesting scenario. SA doesn't use a random generator for obfuscation, so a seed value isn't needed. However, the unicode obfuscation is fairly chaotic, so a small change could cause a large amount of types and methods to change name.
The weaker ascii renaming scheme is much less chaotic, I would suggest using that for this situation.
A random number is used for strings encoding. I think this use case is niche enough that I won't be able to add the seed feature for it, at least in this version. Let me know whether you find it causes a large patch size.
Does anyone else use SA in this kind of scenario?
Red Gate .NET Tools