This is not an issue I expect to be resolved at the moment, but certainly a reminder that it is a valid use-case. It seems customasm is not designed to support single instruction architectures by lack of a true macro mnemonic. The two main issues:

1. You can't define a relative label inside a asm{}
2. $ will always reference the first asm{} IP even when referencing other asm{}