This is what I would use (I fixed your typo).
Simply use a spreadsheet to create a list with 200 lines like this:
Then copy/paste that into the "Pay to" field in Electrum.

It's not that bad: slightly over 6300 bytes for 200 SegWit outputs, and there's no need to use a high fee. Just use the lowest fee possible, it'll confirm in a few days (or weeks).

You're basically creating Bitcoin dust. Even though it doesn't take much fee to fund, spending that many small amounts costs more in fees. The 0.0001 BTC on each physical Bitcoin will be too little to use, because if someone sends it, the receiver will get an even smaller amount and they too have to pay a transaction fee to use/consolidate the funds. Unless someone is going to consolidate many of those small inputs at the same time, there's not much point in using them. I thought you should realize this before turning 0.07 BTC into dust.

This would be interesting, but the only method I've seen so far is custodial. For a physical Bitcoin that's probably going to remain untouched in a long time, that's not a good solution.

I'd suggest using pay to many in electrum

The transaction might still be expensive though, I think that's 80000 bytes and at a high fee of 100 sat per byte it'd cost 0.08btc, at the minimum fee with a longer conf it'd cost only 0.0008 but getting a transaction of that size to confirm at low fees light be harder.

This whole process will be done no more than 6 times (200 sent once, and then 100 sends five more times). I'm making some physical bitcoins.

Is there some kind of use case for going with the LN here?  If so, how would I go about it?