I like this, but I would switch building a new Waystone model for rolling out a new waystone production line for Mordheim. Since our existing waystone model is very well-suited for Mordheim and Mordheim is ripe for purification (having been recently subdued and cleansed of nasties within the last two decades), it's guaranteed to be a very useful effort on our part, and doesn't leave anything to chance.
Personally I think it would be smartest to take the Mordheim Nexus investigate action before trying to set up Waystones nearby. We'd feel like a right lot of ninnies if we set up new Waystones that fed into a Nexus actively powering something dastardly.
By contrast, making a new waystone model has all sorts of points where issues could crop up, and we really wouldn't want to be rushed in dealing with those issues. It also raises all sorts of questions about what sort of new model we want to design, and what circumstances will encourage its use over our existing model. Currently, we're really lacking in a model that can work with the dwarven KAWN, and for that challenge we'd want to investigate as much as possible into the KAWN and ways to link into it. And, arguably, with our existing waystone model being so successful, we ought to give some focus towards waystone nexuses to see if we can potentially recreate them or even come up with a workaround that achieves similar results (in at least some circumstances).
I don't really see how any of those factors mean that a new Waystone design action is a bad idea? The only argument I can see is "well maybe we'll want to make a dwarf waystone at some point if we can figure out how to tie into their network," and I don't disagree, but that only is an argument against designing a new Waystone if you feel that there is a maximum number of times we should take the Build a Waystone action. If you think that more mass-producible Waystones or the barge model are a good idea, then they'll be a good idea regardless of when we get around to designing them, and I'd like to do so sooner rather than later.
As for alternatives to that--we could put a WEB-MAT action into creating a Windherded-enchanted set of robes. Or if we want more time to devote to that task, we could instead spend an action training up one of our skills, like our pistol marksmanship.
Let's see how the purchase turn knife-fight turns out before getting too into the robe design question (begun, the ithilmar wars have), but I will point out that we can't spend a WEB-MAT action on them unless we're committed to doing them with Egrimm, which locks us in to an Ulgu/Hysh combination, and I don't love
the options there; Eyes of Truth, my favorite utility option, was ruled
brainmeats-incompatible. We could just do Radiant Sentinel, I guess, or Blinding Light if we wanted to be ambitious, but neither of those excite me the way "win at spy v spy" did.
Pistol marksmaship seems like a huge waste to me. We almost never use them in combat and we're not close to a skillup, so it's not like we'd even get a point of Martial out of it.
...come to think of it, we haven't codified Knightbringer yet, have we? In-character, it'd be a massive waste if Mathilde died in Ulthuan and never passed on her hard-won discoveries and inventions on Apparition-binding for Ulgu-spellcasters.
Personally, I don't want to codify it until we use it in an actual for-real fight, not just stunting on some greenskins in the Badlands. It would feel weird to me to write up a spell without having used it for real in the field; I also would not have supported codifying Rite of Way based on the testing we did around K8P. The proof of the pudding is in the eating, and the proof of the spell is in deployment in actual mission-critical conditions.