I'm not sure if such a feature is a good way to go.
Currently, it's possible to disable migrations for a whole model or disable one specific migration through the migration management window.
But feature to disable migrations for one table/assoc/etc can lead to several inconsistencies in the project.
Even the current solution where is possible to disable migrations on a whole module can lead to situations when another table is referring table from the disabled module. Such associations/tables will not be correctly created through the migration process.
What is the use-case for such feature? Why you need to disable migration for one specific table? Wouldn't be a solution to create such "static" tables and disable the migration revision for it?