Emotes are a commonly used feature of Channel Point Redemptions requiring messages. Unlike the EventSub Subscription Message events which provide emote ID and placement data, Channel Point Redemption events do not. I propose the following change to the Point Redemption notification payload:

channel.channel_points_custom_reward_redemption.add and channel.channel_points_custom_reward_redemption.update:

{
    "subscription": {
        ...
    },
    "event": {
        ...
        "user_input": {
            "text": "Channel Point Message! finite6ThrowBall",
            "emotes": [
                {
                    "begin": 24,
                    "end": 40,
                    "id": "emotesv2_4133039724974aa59589549eae677d03"
                }
            ]
        },
        ...
    }
}

This allows for a client to properly construct the channel point redemption input, with emote images, similar to the channel.subscription.message event.