Thank you for that and for encouraging me to think about my own macro collection. I have received so much generous help from Martin over the years that I am more than happy to give others any help I can, both with NWP and with Scrivener (though I am less active on that forum than I used to be while still checking it very regularly).
Looking at my personal macros and workflow has made me realise I can prune a lot of unnecessary code. The main macro was first created while Scrivener was pre version 3 and only had presets rather than styles. I realised I could use non-humanly-perceptible colour differences to mark blocks of text and could do a search and replace in NWP for text in those colours and replace them with the same text but marked with the appropriate style… for instance, "Normal" was #FFFFFF (black), Heading 1 was #FFFFFE which was undetectable to me but a different colour to the computer. So my personal macro still has all the necessary code, which is now totally redundant.
I am now experimenting even further and compiling to .MD which I get to open automatically in NWP and, again with great help from Martin, have a macro which turns it into RTF. I can then apply my standard style collection. This means I can write in Scrivener using binder hierarchy to allocate heading levels, simplifying the compile format considerably. That said, lists are still a problem as each list gets its own list style, rather than just applying the usual NWP list styles and levels… my first attempt resulted in 54 separate list styles! However lists are not actually part of my usual texts.
I look forward to hearing how you get on. As for the Lorem Ipsum variation, I took a chunk of text from one of my projects did a fair number of search and replace all firstly of different single letters, and then a fair number of search and replace all of two letter combinations. I can't even remember what the original text was or what or how many operations I did. But yes, it makes a change from Lorem Ipsum.
Mark