Although personally i'd rather avoid dynamic block size altogether since there's concern it could be manipulated by miner who decide which and how much transaction included on their mined block.
Not only that. There is an attack, that could lead to fast verification for the attackers, and extremely slow verification for everyone else.
--snip--
It's also worth to mention miner/pool might offer premium service where they include non-standard transaction. For example, Luxor include almost 4MB NFT on their block[1] where it's available on their professional service category[2].
--snip--
Then, your strategy is simple: always fill the whole block with your dummy transactions, no matter what.
1. It doesn't affect miners, but only competing mining pools (and their block verification time) or other full nodes.
2. It doesn't affect your network, because by knowing master public key, your nodes can skip those transactions as valid.
3. It forces high fees all the time, because even if blocks will be full, then your self-transfer will always fill the remaining space, and make some fee market.
4. It centralizes the network, because if blocks are bigger and bigger, then only your nodes can know upfront, which transactions are fake, and can be skipped as valid. Everyone else waste time on your dummy transaction verification.
But there's downside where overall block propagation is slower since compact block can't be used due to most node doesn't have your transaction on it's mempool.
[1]
https://www.coindesk.com/tech/2023/02/02/giant-bitcoin-taproot-wizard-nft-minted-in-collaboration-with-luxor-mining-pool/[2]
https://docs.luxor.tech/ordinalhub/faq