Hm, yeah, that actually seems like it's working as intended. By default it just shows all active cooldowns and those are cooldowns. The API doesn't tell you what triggered them so I don't think there's a good way to change it for this specific case, but with /cooldowns used this won't happen either.