Hello @StingyJack - the rule is implemented here.
To avoid that you invest time in implementing something that we will refuse, I suggest your first add your new test cases in TestCases/MagicNumberShouldNotBeUsed.cs, open a PR, we can discuss on the specific test cases and agree what should be the change and then you can help with the implementation.
After a discussion with the team we agreed that attributes should not be excluded altogether. However for well-known APIs like DataMember Order (or any attribute with the “Order” parameter), it makes sense to exclude it to limit the noise, by examining the Order = NNN inside the attribute.
The Rule implementation is currently lightweight and we would like to stay it that way, that is the reason why only cases where the name of the parameter is explicitly mentioned should be covered and not all other cases.