this is what I get when I want to debug my plugins with VS 2017 and I hit a breakpoint on plain vvvv newest alpha (35.6) (+ my plugin obviously) all the time. Turning off property evaluation doesn't help, it still times out. I had no such problem with VS 2015 so MS clearly changed something there but you can't download VS 2015 anymore. this doesn't occur during debugging more simple software like vpm. devvvvs, do you have some idea where it can come from?
Maybe the easiest way to reproduce it is opening a dynamic plugin in VS 2017, set a breakpoint somewhere and attach to vvvv.