The only thing I'm aware of is Assassin's alphebetic rage patch, but it applies to the original.
I don't think it got updated for the GBA, which would need to happen to apply it here.

That said, if you supplied a spreadsheet of rages with columns for new and old names as well as columns for whatever facts you'd like to see as a sorting order, it would become the sort of thing that a modder with experience could whip together pretty easily.

(It occurs to me that writing a tool to create a patch from an arbitrary sort order supplied as a CSV file might actually be fun.)

I guess I'll see what I can find, and, barring that, make one myself. Excel isn't all that hard to use. The programming part, though, I'll leave to you guys. Would it be more helpful to have options in one spreadsheet, or across a few? There are a few orders that could be helpful, so I think options are important here. I'm thinking by bestiary number, alphabetically, and by family (either general types or palette swaps).

As far as giving the bestiary an indicator of learned rages, I have no idea, unless you could somehow tie the two together.

The key information needed for a program that fulfils your request would be the Rage's offset in the base Rage list for version being patched and the desired order. I was assuming most of the columns would be for sorting purposes in some other program. We'd need to know or define the column to pull from a spreadsheet.

Ultimately, a string of delimited numbers would suffice, but it's easier to sort if you simply use a spreadsheet.

If the patch generator uses *either* "first in wins" *or* "last overrides any previous" logic, multiple entries wouldn't matter, as only one would get into the list.

Some logic to protect from incomplete lists would need to exist, as well. Two options pop to mind, for that:

1. If count < max, use count for rages, patching to stop at the number given.

2. If count >= max, simply use the rages in order given, but then just fill out the normal sort order from there. Since the previous logic got rid of extraneous entries, you shouldn't be able to exceed the maximum.

The latter seems considerably simpler, though, that depends on how fast you want this thing to run. (In Python, you'd simply use sets for uniqueness and just check against a complete set for completeness. )

I'd need to gather up some info before I could write it, but I could write the bulk of it already. Debating starting on it and simply leaving the output dummied until I do the required research.

The wiki has all the rages in their ROM data order with the old names and new names, but I'm not sure if it's the same as the menu order.
http://finalfantasy.wikia.com/wiki/Rage_(Final_Fantasy_VI_command)

On the topic of an indicator for whether or not you have the rages, I think the absolute optimal, though most likely impossible/incredibly difficult, would be to add a "Shiny effect" when you encounter it, like in pokemon, but I understand this would be incredibly difficult at best.