FYI, here is Brent's support page for sp_blitzIndex.
Scripts like Brent's are based on SQL's built-in "dynamic management views" (DMVs), such as sys.dm_db_index_usage_stats, so let's look at that documentation page:
The counters are initialized to empty whenever the database engine is started. Use the sqlserver_start_time column in sys.dm_os_sys_info to find the last database engine startup time. In addition, whenever a database is detached or is shut down (for example, because AUTO_CLOSE is set to ON), all rows associated with the database are removed.
So the statistics displayed by this DMV (and any fancier procs, like Brent's) are only displaying index usage since the last SQL instance restart.
So yes, as long as the server has been running "long enough"*, it is likely that any indexes with all writes and no reads are good candidates for removal.
* Big caveat: you might think a few weeks or a month is "long enough", but are you sure there isn't some high-level manager somewhere that does a big "end of month" (or "end of quarter") report from your database? Are you super duper sure? Indexes that are only needed for that one rare report are much less likely to show up in this DMV.