Ooh, cool! I know there used to be an issue where analogreads close to eachother could cause what feels like 'interference'.
If you also published your variable values with a spark.publish, then your messages would follow a different path in the cloud than spark.variable, and that would also help distinguish if this is a cloud problem, or a core problem. 
Thanks,
David