It would be lovely to find other elements in the database that may not stop it from working right now but are 'problems waiting to happen'. Other examples might be to search for field names that clash with reserved terms.

Find invalid objects lists each and every proc containing DSQL as invalid. If it cannot evaluate the DSQL it should not include any proc with DSQL in the results, or at least give me the option of filtering them out.
As it is the feature is pretty useless and instead I have to use some other method using the sql_expression_dependencies and dm_sql_referenced_entities views to get what I want.

I would like to be able to run 'Find Invalid Objects' globally as well as for individual databases.
When I look at the output in a csv there is a column for the database name which seems totally redundant when only 1 database is being considered. If this could run on all databases for a server then repeat offenders could be easily identified - the same invalid object in more than 1 place would be a good candidate for cleaning up and with SQL MultiScript this could make a fairly slow and laborious task almost easy.

Enable/create a way to write a script or automate this feature so it can be run frequently (i.e. weekly basis) getting the list of invalid objects as the output instead of manually going to SSMS and right-clicking each and every single database.

Add existence check to the drop statements generated by find invalid objects. If there are several objects that all have the same invalid dependency it would reduce the number of errors after that object has been dropped in the script.