MySQL/Percona Server is taking long and I'd prefer to skip all this waiting even if it means data loss
Unfortunately, you have to let InnoDB purge all its moving parts (Redo Logs, Undo Logs, Dirty Pages, Index Changes, Log Buffer Contents, etc)
Going forward, I recommend the following : Set innodb_max_dirty_pages_pct = 0
By default, innodb_max_dirty_pages_pct is 75. If you set it to 0, it forces the InnoDB Storage Engine to flush every dirty page and its grandmother out of the InnoDB Buffer Pool without any pausing. It will either flush every page or flush it low enough so that new dirty pages enter the Buffer Pool as fast as old dirty pages are flushed out.
Flushing dirty pages and cleaning up transaction is what consumes the most time in a shutdown. Minimizing the number of pages shortens shutdown time.
You can monitor the following status variables

Innodb_buffer_pool_bytes_dirty
Innodb_buffer_pool_pages_dirty

Watch them decrease until it hits zero or levels off. Then, you can issue a shutdown.
Here are additional settings you could use

Set innodb_flush_log_at_trx_commit = 2
Set innodb_write_io_threads = 64

Give it a Try !!!
Afterthoughts
Don't worry about dumping the buffer pool map and reloading. The output file is very small.
SATA/RAID0 sound scary to me. You should be using SAS/RAID10 for InnoDB.
At the very least you think about splitting up InnoDB data, logs, and system tablespaces into separate devices. See my earlier post MySQL on SSD - what are the disadvantages?
You should also think about getting away from Barracuda. See my old post innodb_file_format Barracuda
UPDATE 2014-12-07 18:14 EST
If you want to interrupt an InnoDB purge of everything and you don't want to preserve the data being fixed up, your only option is to set InnoDB Recovery Options. See my post The InnoDB log sequence number is in the future. If you use the innodb_force_recovery options, it may not let you do any more writes of InnoDB. If you a moderate amount of data, you could mysqldump whatever data can come out, shutdown mysqld, delete all data folders (except mysql schema), ib_logfile0, ib_logfile1, and ibdata1, start up mysql, reload data.
I cannot really help you if you have 1TB in a forced recovered state.