I commend your rate of persistence but the ugly facts keep raising their ugly head.
1. It is already development/application capable.
2. MASM in various forms has been around for 30 years.
3. It is designed for assembler programmers, not script kiddies.
4. If you can't manage 64 bit MASM, get a visual garbage generator.

5. If ".if rax {} 1234" is too difficult for you to handle, do it with mnemonics like REAL MEN[tm].
6. If you want a compiler, try CL.EXE, its the industry standard.
7. 64 bit MASM is a standard component of Microsoft VS, it has a massive level of distribution.
After waiting for years for Japheth to actually finish JWASM for 64 bit and still not seeing HJWASM/UASM finished after years of work, I use MASM because its here, now, up and running and it produces what code you can write correctly, no hot little hand holding, easily able to create libraries, does not have a pile of specification clutter that you have to negotiate at the front to get it to build 64 bit code and it has the normal manners of most decent assemblers, truly intolerant, terse notation, bites the hand that feeds it and pelts garbage at you if you get it wrong.

PS : The MASM32 SDK will never be repeated, it came from a world that no longer exists, many clever people worked on it, Iczelion and a number of others on NDAs who will never be identified who contributed code, ideas and testing. What is missing is the collaborative effort as those people no longer exist, I am a dinosaur from that era where people contributed rather than just suck the life out of what was available.