@Lynxrufus(View Post) Changing the current element is a big no. The amount of broken saves would be ridiculous. If you added a new wall, maybe not... Adding a new element/wall isn't a possibility, really. You have 99 channels to play with. So what if you have to heat them all individually - the PROP tool now makes this incredibly easy. I have also seen a script that allows you to place WIFI and set its temperature when you do. https://powdertoy.co.uk/Discussions/Thread/View.html?Thread=10520 As long as you don't leave the game in debug mode, the FPS drop is no issue.
Making wifi blocker possible would make the wifi system a lot more complicated (in terms of programming), and Powder Toy would certainly run more slowly, but it may be possible. However I'm not sure whether this is a good idea - TPT is slow enough already. Try doing what cctvdude99 says - PROP tool, or a Lua script to help set wifi channels.
My current view on the best way to do wifi blocker (which should get around the problem I mentioned in the linked thread, and should minimise the effect on speed):
Make a list of sparked wifi particle locations and channels. Each wifi particle should go through this list and if it is the same channel, check for wifi blocker along the straight line path to the sparked wifi particle location (using interpolation, much like the movement code uses to check for obstacles). If there is no wifi blocker present, release a spark.
If wifi blocker was a wall, that would reduce the time taken to check the path to the sparked wifi particle.