Difficulty in emulating "weaker" OP_SUCCESS and why it should be a real opcode

The proposed new name, OP_RETURN_TRUE, is recommended to reduce confusion and align more intuitively with a potential future renaming of OP_RETURN to OP_RETURN_FALSE. This discussion hints at the idea that such a change, while not urgent due to its lack of direct impact on Bitcoin script's capabilities (since the functionality can be emulated), could significantly aid in preventing code bugs and enhancing clarity within the script.

Additionally, the proposal suggests that this renaming could be considered for inclusion in a significant soft fork, particularly one that introduces tapscript, making it a minor yet potentially valuable addition to a larger update. However, it is also acknowledged that without a pressing need for this renaming due to the absence of immediate functional benefits, the suggestion could remain merely a proposal unless it finds an opportune moment for implementation. This reflects a strategic approach to Bitcoin development, where changes are weighed for their utility and impact before being integrated, even at the level of naming conventions.