MySQL Table not repairing
could this have happened because of a crashed table from doing killall -9 mysqld because it would not shutdown and restart?


Absolutely.  If you kill -9 mysqld and you're using MyISAM tables, you're almost guaranteed to crash some tables unless the server is really, really, really not busy... although the definition of a "crashed" table isn't as catastrophic as it sounds in all cases... it only means, at the simplest level, that the table is not in the state that it should have been in had the server closed it properly.  


  Is there anther way to fix/repair/recover that table?


Have you been through the steps covered in How to Repair MyISAM Tables?

Also, consider these things, which may give you some ideas that could get you on a faster path to recovery if they are not familiar concepts:


With MyISAM tables, everything is in the files.  You could literally take your wp_options.* files (assuming for the sake of discussion that they were not crashed), copy them into a database directory on another MySQL server, SHOW TABLES and you would find that your table is visible and available on that other server.  For future recovery, if you had a slave server, you could shut it down and copy this table's files directly from there back to the master and be back online.  (This is only true for MyISAM and ARCHIVE, not InnoDB, but by contrast, InnoDB tables are extremely immune from this sort of corruption due to a hard/forced shutdown).
The myisamchk utility is not technically a part of the actual MySQL Server itself -- it is a standalone utility built from many of the same underlying libraries, but can be used on a different computer, even without MySQL server installed.  The myisamchk utility has various capabilities and levels of aggression.
You could, therefore, stop MySQL, copy the table files to a different machine -- one with a nice speedy SSD, for example, could make a big difference in recovery time -- and repair the files with myisamchk, then (with the MySQL server stopped again) copy the table files back.  If you have other things running on your MySQL server, you could bring those other things back online while not bogging the server down with this repair.


By contrast, mysqlcheck is nothing but a simple program that connects to your MySQL server using the client libraries and...


  ...uses the SQL statements CHECK TABLE, REPAIR TABLE, ANALYZE TABLE, and OPTIMIZE TABLE in a convenient way for the user.


...so while the two utilities use many of the same methods to repair the tables, they are also fundamentally very different.