You will note that it's not called "Various artist" syntax it's "Multiple Artist". The idea is to have a different syntax if a release has more than one artist for its tracks. Its existence is really a hangover from days before MusicBrainz properly handled having multiple different artists assigned to tracks. Picard considers a release multiple artist if any two track artists are different.
Exactly for the reasons outlined above, in the next Picard release, the separate "multiple artist" syntax will likely be removed and merged into the main one. People expect it to do things that it doesn't really do.
You have a couple of options for dealing with this:
1) If you want your syntax to only deal with "various artists", you could make the syntax explicitly deal with this, i.e. make both of your naming strings have $if($ne(%albumartist%,Various Artists),SA-STUFF,VA-STUFF) sections. I'd change your file naming strings to do this, but they are a pain to do because you've made the syntax quite inconsistent between "single artist" and "multiple artist" releases.
It's a side-issue, but why would you do this? Having VA releases having their multiple discs and release dates in different order than single artist ones? And having the track number and artist in different order in the file name? Obviously it's personal preference, but that seems bizarre to me. The more consistent you make your strings between the two, the fewer problems you will have due to edge cases in the database, and the easier to write/maintain the file renaming strings.
2) In the specific case you mention above with Dizzee Rascal, you could avoid this being considered multiple artist by using the "feat. artists in titles" plugin, which moves the feats to the titles. This will make Picard consider it a "single artist" release. There will, however, still be other edges cases where this won't work (e.g. releases with a bonus track attributed to a collaboration artist)