Should I choose MyISAM for notification tables?
DISCLAIMER : Pure MySQL Perspective
IMHO, you should leave it as InnoDB. MyISAM is not good in high-write situations. Why ?
LOCKING GRANULARITY
Each time you issue an INSERT, UPDATE, or DELETE query on a MyISAM table

The query performs a full table lock
All other queries needing to do the INSERT, UPDATE, or DELETE queries are handled on a first-come first-serve basis

InnoDB has row-level locking. In order to accommodate this, InnoDB caches INSERTs, UPDATEs, and DELETEs in the Buffer Pool, Log buffer, and Undo Logs.
DATA CACHING
MyISAM caches index pages from each MyISAM table's .MYI file in the key buffer.
MyISAM does not cache data. It has to piggyback from the OS for that. You can change the row format of the MyISAM to increase read speed from disk at the expense of double the table's disk usage. Write speed may be adjusted with concurrent INSERTs.
InnoDB caches data and indexes pages in the InnoDB Buffer Pool. You may need a decent size to accommodate data and indexes.
EPILOGUE
You just have to tune some vital settings. Here are some of my past suggestions from the DBA StackExchange.
In favor of InnoDB

Jan 11, 2013 : Very poor insert performance MySQL / Percona Server
Dec 06, 2012 : InnoDB insertion faster
Aug 03, 2012 : Slow insert performance in mysql innodb table for solr indexing
Jul 04, 2012 : Capabilities of InnoDB INSERT Performance

In favor of MyISAM

May 03, 2012 : Which is faster, InnoDB or MyISAM?
Jan 03, 2012 : Optimized my.cnf for high-end and busy server
Sep 20, 2011 : Best of MyISAM and InnoDB
Aug 12, 2011 : Which DBMS is good for super-fast reads and a simple data structure?

Although I lean towards InnoDB, I will leave it to you to decide which storage engine you want to use and tune for.