Ah, yes, if you are already doing multiple runs, then it will take the changed delay variable value at the end of a run and turn it into the actual simulation delays for the following run.
Please note that this behaviour might change with future Brian versions, though : we might raise an error (because the delay is supposed to be constant), or actually take into account delay changes during the run.